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

tiger-js-cli

v0.2.0

Published

Command-line tools for a Tiger app: tiger check (diagnostics), tiger map (a structured JSON map of the app), and tiger skill install (the Tiger Skill for Claude Code).

Readme

tiger-js-cli

Three commands for a Tiger project: two read-only diagnostics, no build, no browser, just the files already on disk, and one that installs the Tiger Skill for Claude Code.

npm install -g tiger-js-cli

tiger check

The same diagnostics the VS Code extension gives a human ("no cell named taks, did you mean task?"), as a command instead of a squiggle only an editor can show:

$ tiger check
pages/tasks.html:22:14  warning  Tiger: no cell named "newTag". Did you mean "newtag"?

0 error(s), 1 warning(s)

Exits with a non-zero code on any diagnostic, error or warning, so it works as a pass/fail gate in a script or an agent loop. Add --json for structured output.

tiger map

The whole shape of the app, read once instead of pieced together file by file: every route, every component (straight from components.json), every cell and its shape, every action, every machine.

$ tiger map
routes:     home, settings, task
components: task-item, empty-state, t-tabs, t-chips, …
cells:      left, filter, search, tasks, task, draft, theme, …
actions:    addTask

--json gives the full structured version, including each cell's declared shape (task becomes { id, text, done, priority, tags }).

tiger skill install

Writes the Tiger Skill, a SKILL.md file Claude Code loads on its own once it recognizes a Tiger project (a <cells> block, a pages/ folder, a components.json), no copy, paste, or prompt engineering needed.

tiger skill install

Installs to ~/.claude/skills/tiger/SKILL.md by default, so it's available in every Tiger project you open from then on, not just the one you ran it from. Pass --project to install it into just the current project instead (.claude/skills/tiger/SKILL.md):

tiger skill install --project

Safe to run again any time: it reports installed, updated, or unchanged and only writes when something actually changed. This is Claude Code specific, it does nothing for other AI coding tools; for those, see AGENTS.md (seeded into every scaffold) or primer.md (paste into any chat).

Usage

tiger check [dir] [--json]
tiger map [dir] [--json]
tiger skill install [--project]

dir defaults to the current folder. check and map expect the usual Tiger project shape: app.html, shared.cells, pages/*.html, components/*.html, components.json, the same convention the router already uses.