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

@zanichelli/email-suggest

v0.1.3

Published

`@zanichelli/email-suggest` suggests a correction for a mistyped email domain (`[email protected]` → `[email protected]`). See [`SPEC.md`](./SPEC.md) §3 for the API.

Readme

email-suggest

@zanichelli/email-suggest suggests a correction for a mistyped email domain ([email protected] → [email protected]). See SPEC.md §3 for the API.

Installing

The package is on the public npm registry. No token or .npmrc is needed:

npm install @zanichelli/email-suggest

Releases are published only by CI, from a v*.*.* tag (.github/workflows/publish.yml, SPEC §9).

Usage

suggest is the only runtime export; Suggestion, its return type, is the only type export. Pass it what the user typed; show the hint if it returns something:

import { suggest } from "@zanichelli/email-suggest";

const s = suggest(input.value);
hint.textContent = s ? `Did you mean ${s.address}?` : "";

It returns a Suggestion or null:

suggest("[email protected]");
// { address: "[email protected]", domain: "gmail.com" }

suggest("[email protected]");
// { address: "[email protected]", domain: "studio-rossi.com" }
  • address is the full corrected address, with the local part exactly as typed (after trimming surrounding whitespace); domain is the corrected domain alone, lowercase.
  • null means no hint: the domain is already known ([email protected]), no known domain is close enough ([email protected]), there is no @ or one side of it is empty (mario, mario@), or the argument is not a string.
  • It never throws, is synchronous and does not touch window or the DOM, so it is safe under server-side rendering.
  • It only suggests: it does not validate syntax and never blocks a submit (SPEC §2). Let the user keep what they typed.

make demo serves a page with the hint live, from examples/demo/, at http://127.0.0.1:5180/ (make demo DEMO_PORT=<n> for another port).

Getting started

This repository follows an agent-native setup. Start with AGENTS.md — the project map and command surface, which points at INSTRUCTION.md for the standard contract (the four execution principles).

Requires pre-commit; the command surface also calls ruff directly, so put it on your PATH (pipx/uv/pip). The JS steps (Biome, tsc, vitest, and the pre-commit hook for src/, test/ and root JSON) run in Docker: make needs Docker Compose, not Node.

make install   # set up git hooks (once)
make quality   # run the full local gate