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

valenv

v1.0.8

Published

Customizable process.env checker with NODE_ENV preset. Has a value validation feature.

Downloads

22

Readme


Process environment checking utility with value validation


Install

npm install valenv --save-dev

Usage A - Development NODE_ENV checker

  • require("valenv").NODE_ENV variable allows process.env.NODE_ENV to be one of these: "development", "production" or "test".

  • If it is undefined or something else, checking it will cause an error.

Where to use?

It's purely a development tool. Use it where process.env.NODE_ENV should be set (webpack.config.js, babel.config.js or other development scripts). Don't use it in a code that will get bundled to enable/disable some parts of code.

Example 1

const NODE_ENV = require("valenv").NODE_ENV;

// Set it like this, via CLI...
process.env.NODE_ENV = "development";
// or just set it like this
NODE_ENV.value = "development";

NODE_ENV.value;
// => "development"

NODE_ENV.is("development");
// => true
NODE_ENV.is("production");
// => false

NODE_ENV.isDev();
// => true
NODE_ENV.isProd();
// => false
NODE_ENV.isTest();
// => false

NODE_ENV.value = "production";
NODE_ENV.is("development");
// => false

Example 2 (Errors)

const NODE_ENV = require("valenv").NODE_ENV;

NODE_ENV.value;
// => Was undefined, shows error and terminates app

NODE_ENV.is("development");
// => Was undefined, shows error and terminates app

NODE_ENV.isDev();
// => Was undefined, shows error and terminates app

NODE_ENV.value = "wrong";
// => Not allowed value, shows error and terminates app

Usage B - Your own checker

You can create your own checkers for any environment variable.

Example

const valenv = require("valenv");

const YOUR_VAR = valenv(
  // will check process.env["YOUR_VAR"]
  "YOUR_VAR",
  // list of allowed values
  ["value1", "value2"],
  // If true will terminate process on error
  true
);

process.env.YOUR_VAR = "value1";

YOUR_VAR.is("value1");
// => true
YOUR_VAR.is("value2");
// => false

YOUR_VAR.value = "value2";
YOUR_VAR.is("value2");
// => true

YOUR_VAR.value = "value3";
// => Not allowed value, shows error and terminates app