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

@mailwoman/fastify

v10.7.0

Published

Fastify plugin for mailwoman — registers POST /parse, /geocode and /poi plus GET /health, and a fastify.mailwoman decorator, over one local runtime pipeline built lazily or injected.

Readme

@mailwoman/fastify

A Fastify plugin that mounts the Mailwoman pipeline as HTTP routes. Register it and your Fastify app parses, geocodes, and answers POI queries locally — no external geocoding service.

npm i @mailwoman/fastify fastify
import mailwomanFastify from "@mailwoman/fastify"
import Fastify from "fastify"

const app = Fastify()
await app.register(mailwomanFastify, { prefix: "/geo", resolveDatabasePath: "/data/candidate.db" })
await app.listen({ port: 8080 })
curl -sX POST localhost:8080/geo/v1/geocode -H content-type:application/json -d '{"address":"350 5th Ave, New York, NY 10118"}'

Routes

Every route is a shared @mailwoman/api operation, so the request and response schemas match the native /v1 surface.

| Route | Body | Returns | | ------------------ | -------------------------- | ----------------------------------------------------------------------------------- | | POST /v1/parse | { address, input_mode? } | The @mailwoman/api parse response (debug is null) | | GET /v1/parse | ?address= | Same as POST /v1/parse | | POST /v1/geocode | { address, input_mode? } | A GeocodeResult (coordinate, resolution tier, admin hierarchy, ranked candidates) | | POST /v1/poi | { query } | The POI intent and results (501 when no poiDatabasePath is configured) | | GET /health | — | { status, uptime_s, version } |

A missing or blank address or query answers 400 { error, detail }; the POI route without a configured database answers 501 { error, detail }. The error envelope matches @mailwoman/api's native /v1 surface.

Options

| Option | Type | Purpose | | --------------------- | ----------------- | ------------------------------------------------------------------------------------------------------------------ | | pipeline | RuntimePipeline | A pre-built pipeline (createRuntimePipeline(...)). The DI / testing path — supply it and no weights are loaded. | | resolveDatabasePath | string | WOF gazetteer (candidate.db / wof.db) for the lazily-built resolver. Omit → parse works, geocode has no coord. | | poiDatabasePath | string | A poi.db layer. Enables POST /v1/poi; wires POI execution on the lazily-built pipeline. | | locale | string | Locale for the lazily-loaded weights + default per-call hint. Defaults to "en-US". | | prefix | string | Fastify register prefix for all plugin routes (e.g. "/geo" exposes POST /geo/v1/parse). |

Supply pipeline to inject your own pipeline. Otherwise the plugin builds one lazily on the first request. Weights and gazetteer data resolve through @mailwoman/neural's standard resolution — the same lookup the CLI and the drop-in servers use.

Decorator

The plugin adds a fastify.mailwoman decorator exposing the same three operations programmatically:

const parsed = await app.mailwoman.parse("350 5th Ave, New York, NY 10118")
const geo = await app.mailwoman.geocode("350 5th Ave, New York, NY 10118")
const poi = await app.mailwoman.poi("coffee near Union Square") // throws if poiDatabasePath is unset

License

AGPL-3.0-only OR LicenseRef-Commercial — see the mailwoman repository.