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

newman-env

v1.0.2

Published

Command-line utility for update Postman Environment

Readme

newman-env

Command-line helper for updating Postman environment variables before running Newman. Use it to patch values in an exported Postman environment JSON so your CI/CD runs always target the right endpoints.

Features

  • Update one or more environment variables from the CLI.
  • Overwrite the source file or write to a separate output path.
  • Leaves values untouched when a key does not exist in the environment file.

Installation

npm install -g newman-env

Usage

Export your Postman Environment as JSON, then run:

newman-env run postman-environments.json --env-var endpoint=http://localhost:3000 --env-var [email protected]

To write to a new file:

newman-env run postman-environments.json -o postman-environments.updated.json --env-var endpoint=http://localhost:3000

Command

newman-env run <environment-file> [options]

Options

  • -o, --output [path] Specify an output environment file path. Defaults to overwriting the input file.
  • --env-var <key=value> Set an environment variable. Repeat for multiple values.

Notes

  • The input file must be a valid Postman environment JSON with a values array of { key, value } entries.
  • If the output directory does not exist, the command fails.

Development

yarn test