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.2.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": {
    "PreToolUse": [
      {
        "matcher": "Bash",
        "hooks": [{ "type": "command", "command": "typos" }]
      }
    ],
    "PostToolUse": [
      {
        "matcher": "Write|Edit|MultiEdit|Bash",
        "hooks": [{ "type": "command", "command": "typos" }]
      }
    ],
    "PostToolUseFailure": [
      {
        "matcher": "Bash",
        "hooks": [{ "type": "command", "command": "typos" }]
      }
    ],
    "SessionStart": [{ "hooks": [{ "type": "command", "command": "typos" }] }],
    "Stop": [{ "hooks": [{ "type": "command", "command": "typos" }] }],
    "SessionEnd": [{ "hooks": [{ "type": "command", "command": "typos" }] }]
  }
}

Claude Code pipes the tool call's JSON payload to the command's stdin. For Write/Edit/MultiEdit, typos reads tool_input.file_path, finds the nearest .nano-staged.json by walking up from that file's directory, and runs whichever configured commands match it.

Bash calls (sed -i, cat > file, ...) name no file, so typos works it out: the PreToolUse hook records when the call started, and the PostToolUse hook asks git (read-only, git --no-optional-locks status) which files are dirty and were modified since, then lints those — each pattern's matching files batched into one command spawn. Files already dirty before the call are left alone, and a call that changed more than 20 files is skipped. PostToolUseFailure covers commands that edited files and then exited nonzero. Outside a git work tree, Bash calls are a no-op.

When Claude is about to end its turn, the Stop hook sweeps every file changed during the session (since the SessionStart hook ran) — a safety net for anything the per-edit hooks missed, like a Bash call over the 20-file cap. Failures exit 2, which keeps Claude working with the errors in front of it; if it's already continuing because of a Stop hook, typos lets it stop rather than loop. After a clean sweep, the next one only looks at files changed since. SessionEnd cleans up the session's marker.

No matching glob pattern or no config found at all is a silent no-op (exit 0).

Every hook invocation pays the command's startup cost, so for the lowest overhead point command at the native binary rather than bunx typos — e.g. build it straight onto your PATH with bun run --filter=@julianelda/typos build:local (~/.local/bin/typos) and wire the hooks once in ~/.claude/settings.json for every repo.

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

typos doctor reports what typos resolves from the current directory, and is the only way to see it — the hooks no-op silently rather than fail when something is missing:

$ typos doctor
git:      /run/current-system/sw/bin/git (PATH)
markers:  /home/you/.cache/typos
worktree: /home/you/work/my-repo
config:   /home/you/work/my-repo/.nano-staged.json

git is looked for in fixed system locations first, then on PATH, skipping any entry that's relative, has a node_modules segment or sits inside the work tree being inspected — so a directory the repo itself controls can't supply it. Without git, Bash and Stop do nothing (Write/Edit/ MultiEdit are unaffected), and doctor exits 1 to say so; every other line is informational and exits 0.

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.