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

envg

v2.0.0-beta

Published

Configure environment variables with Node.js

Readme

envg

Configure environment variables with Node.js

Getting started

  1. npm i envg
  2. prepare env/example.js file like that
module.exports = {
  HOGE: 'hogehoge',
  FUGA: 'fugafuga',
  NODE_ENV: 'example',
};
  1. Configure npm-scripts of your package.json like that
"scripts": {
  "start": "envg example <your_command>"
}
  1. You can use environment variables defined by env/example.js in any your command!
# with process.env
$ npx envg example node -e "console.log(process.env.HOGE)"
>> hogehoge

# with reuire('envg')
$ cat print.js
const { env } = require('envg');
cnosole.log(env.HOGE);

$ npx envg example node print.js
>> hogehoge

# with non-js file
$ cat print.sh
echo $HOGE

$ npx envg sh print.sh
>> hogehoge

Advanced usage

Overwrite environment variable

env/<env_name>.js file can be overwritten by environment variable, these values works as default. For example, if you have such a env/example.js file:

module.exports = {
  HOGE: 'hogehoge',
  FUGA: 'fugafuga',
  NODE_ENV: 'example',
};

You can overwrite these environment keys (HOGE, FUGA, NODE_ENV):

$ npx envg example node -e "console.log(process.env.HOGE)"
>> hogehoge

$ HOGE=overwritten npx envg example node -e "console.log(process.env.HOGE)"
>> overwritten

You don't need to write HOGE: process.env.HOGE || 'hogehoge' or something in env file.

Define environment variable with non-default value

You may require environment variable which has non-default value but used in application. For example, you have secret token which is passed in environment variable, but not exposed in source code.

In that case, you can configure such a variable with undefined value, like that (env/secret.js):

module.exports = {
  SECRET_VALUE: undefined,
};

This SECRET_VALUE should be passed as environment variable, otherwise envg will be failed for preventing your command runs with non SECRET_VALUE value. You don't require your own validation logic for process.env.SECRET_VALUE in that case.

# it will be failed before `npm start`
$ npx envg secret npm start

# it will work well
$ SECRET_VALUE=XXX npx envg secret npm start

envg