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

@quantojs/libpostal

v0.6.0

Published

Mailing addresses for quanto, parsed by libpostal: an external codec that turns libpostal's output into a normalized address.

Readme

@quantojs/libpostal

Mailing addresses for quanto, parsed by libpostal: 1600 amphitheatre pkwy, mountain view, california 94043 becomes a normalized address you can store, validate and format back.

import { address } from '@quantojs/libpostal';
import postal from 'node-postal';

const shipping = address({
  libpostal: async (text) => postal.parser.parse_address(text),
  defaultCountry: 'US',
});

await shipping.parse('1600 amphitheatre pkwy, mountain view, california 94043');
// { ok: true, value: { lines: ['1600 amphitheatre pkwy'], locality: 'mountain view',
//                      region: 'CA', postalCode: '94043', country: 'US' }, … }

shipping.format({ lines: ['Hauptstraße 5'], locality: 'Berlin', postalCode: '10115', country: 'DE' });
// 'Hauptstraße 5, 10115 Berlin, Germany'

You run libpostal

libpostal is an open-source statistical address parser trained on over a billion addresses, for most countries. It runs on CPU and is fast (10–30k addresses a second per thread), but its model is about 2 GB, so this package doesn't depend on it: you pass a libpostal function from text to libpostal's [{ label, value }]. Run it on a server, never in a browser.

  • In-process, with node-postal (needs libpostal installed):

    address({ libpostal: async (text) => postal.parser.parse_address(text) });
  • As a service, such as pelias/libpostal-service in Docker:

    address({
      libpostal: async (text, { signal }) => {
        const res = await fetch(`http://libpostal:4400/parse?address=${encodeURIComponent(text)}`, { signal });
        if (!res.ok) throw new Error(`libpostal answered ${res.status}`);
        return res.json();
      },
    });

Reject when libpostal can't answer: a failed service is never turned into issues. In a browser field, the codec's parse is a call to your server, which runs this codec.

What you get

  • Address: lines (building, street, unit, PO box, in the order written), and optionally dependentLocality, locality, region, postalCode and country (ISO 3166-1 alpha-2).
  • Text as typed. libpostal lowercases; the codec restores what was typed, and doesn't guess capitals.
  • Normalized regions, postal codes and countries: California → CA (US, Canada, Australia), sw1a2aa → SW1A 2AA (countries with one postal format), Deutschland, UK, USA → DE, GB, US.
  • defaultCountry for addresses that don't name one. Formatting leaves it out, and names other countries in the reader's language (ctx.locale).
  • Issues: unparseable with no street line, no city or postal code, or an unknown country.
  • Formatting in each country's order: …, Mountain View, CA 94043, …, 10115 Berlin, …, London SW1A 2AA.

libpostal splits an address into parts; it doesn't check the address exists, and has no completions. For those, use a geocoding API in your own external codec. The design is in the repository's DESIGN.md, "Addresses".

quanto is a peer dependency.