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

@keyframerdev/wizard

v0.1.0

Published

Sets up the Keyframer Inspector and Motion Vitals in a React Native or Expo app, step by step, and waits for the first message to prove it works

Readme

@keyframerdev/wizard

Sets up the Keyframer Inspector and Motion Vitals in a React Native or Expo app, step by step, then waits for the app's first message to prove it works.

npx @keyframerdev/wizard

npx @keyframerdev/wizard: what to set up, where to see the Inspector, the Motion Vitals key, each change as a diff, the install, then the app's first message

Run it in your app's folder (or pass --root apps/mobile in a monorepo). It needs Node 20 or later.

What it does

  1. Finds your app: Expo or bare React Native, the package manager (from the lockfile, the workspace's in a monorepo), expo-router or React Navigation, the Babel config and the entry file. It warns when git has uncommitted changes, so the edits are easy to review.
  2. Asks what to set up: the Inspector (a motion debugger for development builds), Motion Vitals (slow frames and janky animations from production), or both; where you want to see the Inspector; and your Motion Vitals key, pasted or found by signing in through the browser.
  3. Shows every change as a diff before writing it, and writes each file on your yes.
  4. Installs the packages, and what they need that your app doesn't have.
  5. Sets up your coding agent (Claude Code, Cursor) with the Inspector's MCP server, if you want.
  6. Waits for your app: start or reload it, and the wizard shows the Inspector's first hello and Motion Vitals' first session.

Running it again finds everything in place and changes nothing.

What it changes

Only these, and only what is missing. Nothing in node_modules, ios/ or android/.

| | | | --- | --- | | package.json | @keyframerdev/inspector (dev dependency) and @keyframerdev/vitals (dependency), with npx expo install in Expo apps, else your package manager. Also Reanimated 4 and react-native-worklets when the app has neither, expo-constants for Vitals' version and build, and babel-preset-expo when it creates your first Babel config | | babel.config.js | @keyframerdev/inspector/babel in development only and @keyframerdev/vitals/babel, before the worklets plugin, which stays last. A config it can't edit safely (branches, JSON with comments, plugins built in code) is left alone, with the snippet to paste | | keyframer.ts | One new file the wizard owns (src/keyframer.ts when the app has src/; .js in JavaScript apps): the Inspector's start, in development only, and Motion Vitals' start | | The entry | One import of that file, or with navigation, the edit below | | Navigation | expo-router: useNavigationContainerRef() and useKeyframer(navigationRef) at the top of app/_layout. React Navigation: ref={navigationRef} on your NavigationContainer (or your own ref, followed to where it is made). Several containers, or a wrapper of your own: the snippet and where to put it | | <VitalsRoot> | Around what your root component returns, when you say yes |

Edits keep your file's formatting: only the lines that change are printed, in your file's quotes, semicolons and indentation.

Both packages are JavaScript only: no native module, no config plugin, no rebuild. When the wizard installs Reanimated or worklets (native modules), it says what to rebuild.

Options

| Flag | | | --- | --- | | --products inspector,vitals | What to set up (default: ask) | | --view devtools\|desktop\|editor | Where to see the Inspector: Expo's dev tools (shift+m in Metro), the Keyframer Inspector desktop app, or the Keyframer editor | | --code ABC234 | The pairing code the editor's Inspector panel shows (--view editor) | | --key kfp_live_… | The Motion Vitals project's field key | | --auth paste\|browser | Without --key: paste the key, or sign in through the browser | | --vitals-root, --no-vitals-root | Wrap the app in <VitalsRoot>, or don't (default: ask) | | --agents claude-code,cursor, --no-agents | Set up these agents' MCP config, or offer none | | --metro http://localhost:8095 | Metro's address, when it isn't on 8081-8090 | | --root <dir> | The app's folder | | --api <url>, --app <url> | https://api.keyframer.dev and https://keyframer.dev (or KEYFRAMER_API_URL, KEYFRAMER_APP_URL; KEYFRAMER_VITALS_URL for the ingest server) | | --yes, -y | No questions: the defaults, and an error naming the flag where there is none | | --dry-run | Show every change, write nothing, install nothing | | --skip-install | Print the install commands instead of running them | | --skip-verify | Don't wait for the app | | --install-desktop | Download and install the desktop app if it's missing, without asking |

Exit codes: 0 done, 1 failed, 2 bad usage (or a question --yes can't answer), 130 cancelled.

For agents and CI

With --yes (or without a terminal) the wizard asks nothing. A question with a default takes it; one without stops with exit code 2 and the flag that answers it.

npx @keyframerdev/wizard --yes --products inspector --view devtools
npx @keyframerdev/wizard --yes --products inspector,vitals --view desktop --key kfp_live_… --no-agents
npx @keyframerdev/wizard --yes --dry-run --products inspector          # what it would change

Develop

bun run wizard --dry-run --root ../my-app      # from source
bun run test && bun run typecheck && bun run lint
bun run build                                  # dist/cli.js and publish/

License

MIT