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

@geomelon/data-query

v1.0.0

Published

Loader and query interface for Geomelon per-country data packages (@geomelon/<country>) — filter cities and regions instead of scanning a bare JSON array

Readme

@geomelon/data-query

Loader and query interface for Geomelon per-country data packages (@geomelon/<country>). Every generated country package depends on this and re-exports a ready-made dataset instead of a bare JSON array.

Usage

const spain = require('@geomelon/spain')

spain.cities({ name: 'Barcel' })          // prefix match, checks every translation too
spain.cities({ minPopulation: 1000000 })
spain.cities({ regionId: 'region-1', limit: 10 })
spain.city('Q1492')                       // by Geomelon id or Wikidata id
spain.regions({ name: 'Cataluña' })
spain.country                             // country-level fields
spain.meta                                // generatedAt, recordCount, license, source

Or build a dataset directly from a raw payload (e.g. downloaded separately, or from a package whose main you didn't use):

import { createGeomelonDataset } from '@geomelon/data-query'
import data from '@geomelon/spain/data.json'

const spain = createGeomelonDataset(data)

Filters

cities(filter?): | field | type | matches | |---|---|---| | name | string | case-insensitive prefix match against the primary name and every translation | | regionId | string | exact match | | minPopulation / maxPopulation | number | inclusive range | | language | string | city has a translation in this language | | settlementType | string | exact match against one of the city's settlement types | | limit | number | caps the result count |

regions(filter?) supports name and limit.

License

MIT (this package's code). The data shipped inside each @geomelon/<country> package is CC0-1.0 — see that package's own LICENSE.