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

@testsnag/cli

v0.1.7

Published

Upload a mobile build, point tests at it, and run them.

Readme

TestSnag CLI

Upload a mobile build, point tests at it, and run them.

npx @testsnag/cli

Getting started

Create a token in your workspace settings, under API tokens, then:

npx @testsnag/cli login

The token is stored in ~/.testsnag/config.json. In CI, set TESTSNAG_TOKEN instead and skip the login step.

Commands

| Command | What it does | | -------- | ---------------------------------------------- | | login | Store an API token and the installation URL | | run | Trigger tests that already have a build | | update | Upload a build, bind it to tests, and run them |

Run with no command to pick interactively.

Options

| Flag | Meaning | | ------------------- | ------------------------------------------------------------- | | --test <id\|name> | The test id, or its full name. Repeat the flag for each test. | | --build <path> | The build file to upload | | --run | Run the tests after updating | | --wait | Block until runs finish, exit non-zero on failure | | --token <token> | Overrides TESTSNAG_TOKEN | | --url <url> | The TestSnag installation | | --json | Machine readable output, implies non-interactive |

In CI

Supply every input as a flag and there is no prompt, so it runs without a TTY:

TESTSNAG_TOKEN=$TESTSNAG_TOKEN npx @testsnag/cli update \
    --build ./android/app/build/outputs/apk/release/app-release.apk \
    --test "Checkout smoke" --test "Sign up" \
    --run --wait --json

The exit code is non-zero when a run fails, so the pipeline stops.

Builds

iOS takes a zipped simulator build (.zip, .tar.gz, .tgz), produced with xcodebuild -sdk iphonesimulator. Android takes an .apk or .apks.

An .ipa or an .aab can be uploaded and stored, but not bound to a test: an .ipa is built for device hardware and a simulator cannot run it, and an .aab is not installable until bundletool build-apks --mode=universal converts it.

Interactively, the CLI lists build artifacts it finds in the working directory and the usual output directories, newest first. That covers Gradle and Xcode as well as Flutter (build/app/outputs/flutter-apk, build/ios/iphonesimulator) and React Native (ios/build/Build/Products/Debug-iphonesimulator).

To upload a build without pointing any test at it, choose Just upload it when asked, or pass --no-bind. The file lands in your Files library, ready to bind later.

Development

npm test
npm run format

No build step, no TypeScript. Node 20 or newer.