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 🙏

© 2024 – Pkg Stats / Ryan Hefner

cross-env-test

v0.1.1

Published

Test environment variables across operating system environments

Downloads

653

Readme

cross-env-test

This command line tool works on *NIX (including OS X) and Windows. This tool checks to see if an environment variable is set to a given value:

cross-env-test NODE_ENV=testing

if NODE_ENV is set to testing the program will exit with 0 otherwise it will exit with a non-zero value

The logic is very close to:

if (process.env.NODE_ENV === 'testing') {
  process.exit(0);
} else {
  process.exit(1);
}

Usage I use this in my npm scripts:

{
  "scripts": {
    "postinstall": "cross-env-test NODE_ENV=testing || npm run build"
  }
}

Why?

Sometimes it's advantages to only run certain npm scripts sometimes. For example when running an install in an automated test environment.

Limitations

  • only supports '=' and '!=' operators
  • environment variable must be on the left hand side of the operator
  • arguments not in the form of lh=rh or lh!=rh will cause the program to exit with an error code
  • chained arguments are implicitly &&ed together
  • if there is interest we can add a --or modifier

License

MIT