• replace wifi-location with cross-platform alternative

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

runtime error that happens on occassion when handleCoords tries to manipulate a lat/lng object that doesn't have a lat/lng due to API miscommunication.

/Users/mshertzberg/.nvm/versions/node/v6.8.1/lib/node_modules/surger/lib/index.js:90
      var _ref$lat = _ref.lat;
                         ^

TypeError: Cannot read property 'lat' of undefined
    at Surger.handleCoords (/Users/mshertzberg/.nvm/versions/node/v6.8.1/lib/node_modules/surger/lib/index.js:90:26)
    at /Users/mshertzberg/.nvm/versions/node/v6.8.1/lib/node_modules/surger/lib/index.js:170:58

Any personal experiences using the node module? Does it work for you? Does it not work for you? Could it be improved? Are you constantly having location errors? Where are you located?

Thanks!!