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

@reapi/cli-next

v0.0.1

Published

ReAPI CLI tool for running API tests and managing test deployments

Readme

@reapi/cli-next

ReAPI CLI tool for running API tests and managing test deployments.

Installation

npm install -g @reapi/cli-next
# or
yarn global add @reapi/cli-next
# or
pnpm add -g @reapi/cli-next

Usage

Running Tests

# Run tests from a local deployment file
reapi test run ./deployment.json

# Run tests from a remote deployment
reapi test run remote://deployment-id

# Run tests with output directory
reapi test run ./deployment.json --output ./test-results

# Run tests with environment variables
reapi test run remote://deployment-id --env ./env.json

# Run tests with configuration file
reapi test run --config ./reapi.yaml

Access Token Options

You can provide access tokens in several ways (in order of priority):

  1. Direct CLI token:
reapi test run remote://deployment-id --access-token "your-token"
  1. Config file token (reapi.json/yaml):
{
  "accessToken": "your-token"
}
  1. Custom environment variable:
# Set custom environment variable
export MY_TOKEN="your-token"
reapi test run remote://deployment-id --access-token-env MY_TOKEN

# Or in config file
{
  "accessTokenEnv": "MY_TOKEN"
}
  1. Default environment variable:
export REAPI_ACCESS_TOKEN="your-token"
reapi test run remote://deployment-id

Configuration File

You can use either JSON or YAML for configuration:

# reapi.yaml
target: ./deployment.json
output: ./test-results
env: ./env.json
report: junit,html
reportPath: ./reports
serverUrl: https://api.example.com
throwOnFailure: true
// reapi.json
{
  "target": "./deployment.json",
  "output": "./test-results",
  "env": "./env.json",
  "report": "junit,html",
  "reportPath": "./reports",
  "serverUrl": "https://api.example.com",
  "throwOnFailure": true
}

Options

  • --target <path> - Test target: local JSON file or remote://uri
  • -o, --output <path> - Output directory path
  • -a, --access-token <token> - Access token for remote deployments
  • --access-token-env <env-name> - Environment variable name for access token
  • -e, --env <path> - Environment file path (JSON/YAML)
  • -r, --report <types> - Report types (junit,html)
  • --report-path <path> - Directory for report files
  • --server-url <url> - ReAPI server URL
  • -t, --throw-on-failure - Exit with error code on test failure
  • -c, --config <path> - Config file path (JSON/YAML)

Development

# Install dependencies
pnpm install

# Run tests
pnpm test

# Build
pnpm build

# Run in development mode
pnpm dev

License

ISC © PeiSong