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/vitals-cli

v0.1.0

Published

Motion Vitals symbol uploads: dSYMs, Flutter split debug info, R8 mappings and React Native sites files, for keyframer.dev

Readme

@keyframerdev/vitals-cli

keyframer-vitals: symbol uploads for Motion Vitals, so slow frames from release builds are shown with function names, files and lines. Node 18 or later; no native modules (the symbol reader is WebAssembly, inside the package).

npx @keyframerdev/vitals-cli symbols upload --dsym path/to/App.app.dSYM          # iOS
npx @keyframerdev/vitals-cli symbols upload --elf build/debug-info                # Flutter Android (--split-debug-info)
npx @keyframerdev/vitals-cli symbols upload --dsym build/debug-info/app.ios-arm64.symbols   # Flutter iOS (Mach-O)
npx @keyframerdev/vitals-cli symbols upload --mapping app/build/outputs/mapping/release/mapping.txt \
  --app-version 1.4.0 --build 212                                                 # Android R8
npx @keyframerdev/vitals-cli symbols upload --rn-sites .keyframer/sites-1.4.0+212.json   # React Native hashSites
npx @keyframerdev/vitals-cli symbols inspect path/to/App.app.dSYM                 # debug ids and architectures

The upload key is the project's CI key (kft_…), in --key or KEYFRAMER_VITALS_UPLOAD_KEY. --dry-run --out <dir> writes what would be uploaded instead. keyframer-vitals --help lists every option.

Symbol files are read on your machine: functions and line tables from DWARF (dSYMs, fat binaries per architecture, ELF), classes and line ranges from R8 mappings, then split into small JSON chunks. Only those chunks are sent. Swift names are demangled with xcrun swift-demangle when it is available (macOS with Xcode); elsewhere they are uploaded mangled.

Development

bun run test            # golden fixtures in ../protocol/fixtures/vitals/symbols
bun run build           # dist/cli.js
bun run build:wasm      # after changing ../../symbols (Rust); writes src/symbolsWasm/

MIT