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

@sophonz/cli

v0.1.0

Published

Sophonz command line tool: upload source maps, dSYMs and R8 mappings for symbolication

Readme

@sophonz/cli

한국어

Uploads the files Sophonz needs to symbolicate stack traces: web source maps, iOS dSYMs and Android R8/ProGuard mappings.

Files are kept per version of your app. Source maps belong to a web version (the browser SDK's web.version); dSYMs and mappings belong to an app version (service.version).

Install

npm install -D @sophonz/cli

Requires Node.js 20 or later.

Authentication

Create an access token in Sophonz under Settings > app > Access tokens. A token belongs to one app, so no command takes an app name.

export SOPHONZ_TOKEN=sophonz_pat_...

| Option | Environment | Default | |--------|-------------|---------| | --token | SOPHONZ_TOKEN | — | | --api-url | SOPHONZ_API_URL | https://app.sophonz.ai | | --dry-run | — | off |

Web source maps

sophonz upload-sourcemaps --path dist --web-version 2026.09.14-3

Next.js (the scripts are served from /_next/static):

sophonz upload-sourcemaps --path .next/static --url-prefix _next/static \
  --web-version "$WEB_VERSION"
  • --web-version must equal what the page reports: the SDK's webVersion option, or appVersion when that is unset. Set both from the same variable in CI.
  • Each map is uploaded under the path of the script that references it, read from the script's sourceMappingURL. Bundlers that give the map a different name than the script (Next.js 16 Turbopack) are handled, as are inline maps.
  • Upload before or right after deploying; a trace is matched when it is opened.

iOS dSYM

sophonz upload-dsym --file "$DWARF_DSYM_FOLDER_PATH" --version 1.4.0 --build-id 120

--file takes a .dSYM bundle, a directory containing bundles (every one is zipped and sent together), or an existing zip. Traces are matched by image UUID, so frameworks with their own dSYM are covered.

Android mapping

sophonz upload-mapping --file app/build/outputs/mapping/release/mapping.txt --version 1.4.0

--type PROGUARD for a legacy ProGuard mapping. --build-id matches the app.build_id the SDK reports and can replace --version. Projects using the Sophonz Gradle plugin upload mappings automatically.

GitHub Actions

- name: Upload source maps
  env:
    SOPHONZ_TOKEN: ${{ secrets.SOPHONZ_TOKEN }}
  run: npx @sophonz/cli upload-sourcemaps --path dist --web-version "${{ env.WEB_VERSION }}"