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

@julianelda/typos

v1.0.0

Published

Lint/format a single file directly, without touching git — a nano-staged-config-compatible replacement for the naive nano-staged-in-a-hook approach

Readme

typos

In all things shewing thyself a pattern of good works.

License: MIT npm version

Lint/format a single edited file — safe for Claude Code hooks, no git involved.

Reads a repo's existing .nano-staged.json and runs the matching lint/format commands against a single file path, replicating nano-staged's command execution semantics without any git staging — safe to call concurrently from a Claude Code PostToolUse hook.

Usage

Wired up as a Claude Code hook, in .claude/settings.json:

{
  "hooks": {
    "PostToolUse": [
      {
        "matcher": "Write|Edit|MultiEdit",
        "hooks": [
          {
            "type": "command",
            "command": "typos"
          }
        ]
      }
    ]
  }
}

Claude Code pipes the tool call's JSON payload to the command's stdin; typos reads tool_input.file_path from it, finds the nearest .nano-staged.json by walking up from that file's directory, and runs whichever configured commands match it. Anything else — a Bash call, no matching glob pattern, no config found at all — is a silent no-op (exit 0).

Called directly, e.g. to try a config against one file:

echo '{"tool_name":"Write","tool_input":{"file_path":"src/index.ts"}}' \
  | typos

-c/--config overrides auto-discovery with an explicit config path:

echo '{"tool_name":"Write","tool_input":{"file_path":"src/index.ts"}}' \
  | typos --config ./.nano-staged.json

A failing command's exit code and stderr are surfaced as Claude Code's "blocking feedback" (exit code 2), so Claude sees the actual lint/format error and can self-correct.

See CLAUDE.md for the full design and current implementation status.