npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

omnigeo

v0.0.1

Published

node.js geocoder with pluggable geocoding services.

Readme

omnigeo

omnigeo is a node.js library for geocoding addresses with pluggable services. There are no production dependencies outside of node.js itself. The current state of this library is very alpha. You have been warned.

Usage

Defaults to google:

geocoder().geocode('New York, NY', function(res) {
  console.log(res)
  // { lat: 40.71, lon: -74.00, service: 'google' }
}

Defining a service:

geocoder({service: 'mapquest'}).geocode('New York, NY', function(res) {
  console.log(res)
  // { lat: 40.71, lon: -74.00, service: 'mapquest' }
}

Services

  • Google Maps
  • Mapquest Open
  • Nominatim (OpenStreetMaps geoder)
  • Yandex
  • DataScienceToolkit

Why these services?

The short answer is that they all work without an api key. This is great for several reasons but ultimately allows a very simple interface to these services.

Contributing

If you have an interest in working on something or fixing a bug, file an issue.

Add a service

The following is the format for a service. The key you define will be how the service is referenced everywhere. Look at the services.json file for examples.

The required keys you need to provide:

  • base: the portion of the url after the protocol and before any parameters
  • lat/lon: using response as the json response from the service you must specify the path to get to the lat/lon values.
  • addressParam: what the service uses for the query parameter for the address in question.

Optional:

  • params: if the service requires any other parameters to be included to perform a proper request for their service.
"nominatim": {
  "base": "nominatim.openstreetmap.org/search",
  "lat": "response[0].lat",
  "lon": "response[0].lon",
  "addressParam": "q",
  "params": {
    "format": "json"
  }
}

I have also added an integration test for each of the services just to make sure that they are all still working before I push code. Upon adding a service please include on in a pull request (I will be glad to help with doing this).

License

BSD