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

@proximap/core

v1.0.1

Published

Core geospatial engine for proximap: geocoding, nearby places, and ranking. OpenStreetMap by default, pluggable providers.

Readme

@proximap/core

Geospatial engine for proximap: geocoding, nearby search, travel-time ranking, walkability, gap detection, reachability, location comparison, and errand planning. OpenStreetMap by default (no API keys), with pluggable geocoding / places / routing providers. Zero runtime dependencies.

Install

npm install @proximap/core

Usage

import { findNearbyAmenities } from '@proximap/core';

const { origin, results } = await findNearbyAmenities('Brandenburg Gate, Berlin', {
  radiusMeters: 800,
  categories: ['food', 'transport'],
  limit: 15,
});

console.log(origin.displayName);
for (const r of results) {
  console.log(`#${r.rank} ${r.name ?? r.category} — ${r.distanceMeters} m`);
}

Bring your own provider

import { findNearbyAmenities, type PlacesProvider } from '@proximap/core';

const myProvider: PlacesProvider = {
  name: 'my-source',
  async findNearby(center, options) {
    /* return Poi[] */
  },
};

await findNearbyAmenities('Tokyo Station', { places: myProvider });

findNearbyAmenities also takes filters (diet/payment/wifi/wheelchair…), accessible (step-free-first ranking), open ('now' or { at }, keeping unknown-hours places labelled rather than dropped), rankBy: 'travelTime' with a routing engine, and explain (a short rankingReason per result).

Beyond "what's nearby"

import {
  detectGaps,
  walkabilityScore,
  reachableAmenities,
  compareLocations,
  planErrands,
  disambiguateLocation,
} from '@proximap/core';

// What everyday amenities are missing? (absence framed as "not found in OSM")
const gaps = await detectGaps('Brandenburg Gate, Berlin', { thresholdMeters: 1000 });

// How walkable is it? 0-100 with a transparent, tunable breakdown + confidence.
const walk = await walkabilityScore('Brandenburg Gate, Berlin');

// What's within a 15-minute walk? (real isochrone where available)
const reach = await reachableAmenities('Brandenburg Gate, Berlin', { within: 15, mode: 'walk' });

// Compare neighbourhoods; plan the shortest one-per-category errand trip.
const cmp = await compareLocations(['Prenzlauer Berg, Berlin', 'Marzahn, Berlin']);
const trip = await planErrands('Alexanderplatz, Berlin', { categories: ['pharmacy', 'atm', 'grocery'] });

// Don't guess a wrong location — surface candidates when a name is ambiguous.
const geo = await disambiguateLocation('Springfield'); // → { ambiguous, best, candidates }

Offline & export

import { snapshotArea, DatasetPlacesProvider, toGeoJSON } from '@proximap/core';

const dataset = await snapshotArea('Montmartre, Paris', { radiusMeters: 1500 });
const offline = new DatasetPlacesProvider(dataset); // findNearby with no network
const fc = toGeoJSON(await findNearbyAmenities('48.8867,2.3431', { places: offline }));

Bring your own provider

import { findNearbyAmenities, type PlacesProvider, type RoutingProvider } from '@proximap/core';
// Implement PlacesProvider / GeocodingProvider / RoutingProvider and pass via
// findNearbyAmenities(query, { places, geocoder, routing }).

Also exported: providers (NominatimGeocoder, OverpassPlacesProvider, ValhallaRoutingProvider, OsrmRoutingProvider, HaversineRoutingProvider), rankByProximity, nearestMatchingPoi, isOpenAt, toGeoJSON/toCSV, pointInPolygon, categorize, haversineMeters, formatDistance, formatDuration, CATEGORIES, and the domain types. See the main README.

License

MIT