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

geocodekit

v1.2.0

Published

Type-safe geocode / reverse-geocode helper for Mapbox, Google Maps, and Geocod.io — never throws.

Readme

geocodekit

Type-safe geocode / reverse-geocode universal helper that never throws.

Install

npm install geocodekit
# or
bun add geocodekit

Quick start

import { createGeocoder } from 'geocodekit'
import { mapbox } from 'geocodekit/mapbox'
import { google } from 'geocodekit/google'

const geo = createGeocoder({
  providers: [
    mapbox({ apiKey: process.env.MAPBOX_TOKEN! }),
    google({ apiKey: process.env.GOOGLE_MAPS_KEY! }),
  ],
})

const { data, error } = await geo.geocode('1600 Amphitheatre Parkway, Mountain View, CA')
if (error) {
  console.log(error.code, error.message)
} else {
  console.log(data.formatted, data.coordinates)
}

Import only the providers you use (geocodekit/mapbox, geocodekit/google, geocodekit/geocod) so unused adapters tree-shake away.

API

geocode / reverseGeocode

Scalar or array. Arrays return per-item GeoResults.

await geo.geocode('Berlin')
await geo.geocode(['Berlin', 'Paris'], {
  mode: 'auto', // batch if provider supports it, else paced loop
  rateLimit: { maxPerMinute: 500 }, // defaults to provider's rate limit
  concurrency: 2, // defaults to 1
})

await geo.reverseGeocode({ lat: 52.52, lng: 13.405 })

Structured input:

await geo.geocode({
  streetNumber: '1600',
  street: 'Amphitheatre Parkway',
  locality: 'Mountain View',
  region: 'CA',
  country: 'US',
})

Options that narrow types

  • require: ['street', 'county', 'name', …]: missing fields → MISSING_FIELDS; success narrows those keys on Place / components
  • minAccuracy: 'rooftop': too coarse → LOW_ACCURACY; success narrows accuracy

name is the place / POI / addressee label (Geocod addressee, Mapbox non-address feature labels). Google Geocoding often omits it. New components: unit, neighborhood, county.

withAddress

const pin = { id: 1, lat: 40.7, lng: -74 }
const out = await geo.withAddress(pin)
// out.address: GeoResult<Place>

const nested = await geo.withAddress(
  { id: 1, location: { lat: 40.7, lng: -74 } },
  { getCoords: (x) => x.location },
)

Fallback

Default: try next provider on any error except BAD_REQUEST and ABORTED.

createGeocoder({
  providers: […],
  shouldFallback: (e) => e.code === 'RATE_LIMIT' || e.code === 'NETWORK',
})

License

MIT