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

preset-process-env

v1.0.0

Published

Preset node process.env before run scripts

Downloads

11

Readme

Build Status Codacy Badge

preset-process-env

Preset node process.env before run scripts

Install

npm i preset-process-env

Usage

Basic

Assume there are 2 environments, prod and test. Build your source code by npm run build command.

"scripts": {
	"build": "your command",
	"build:prod": "preset-process-env build prod",
	"build:test": "preset-process-env build test"
}

preset-process-env should

  1. Find the corresponding environment config file under /envs directory. File name is .env.xxx.js, xxx is from command line,

    eg. preset-process-env build prod -> /envs/.env.prod.js
    eg. preset-process-env build test -> /envs/.env.test.js

  2. Read the export JSON object from environment js file, copy properties to process.env,
  3. Run command by given command line,

    eg. preset-process-env build prod -> npm run build
    eg. preset-process-env test prod -> npm run test

Additional

Variables also can be passed by command line,

eg. preset-process-env build prod VAR-A=abc -> process.env['VAR-A'] // output: "abc"
eg. preset-process-env build prod VAR-B=false -> process.env['VAR-B'] // output: false
eg. preset-process-env build prod VAR-C -> process.env['VAR-C'] // output: true

  • true/false should be converted to boolean value,
  • true is optional.

Sample

  • /envs/.envs.test.js
    module.exports = {
    	// environment name
    	ENV_NAME: 'TEST',
    };
  • Command line,
    preset-process-env build test
  • In your source code,
    console.log(process.env.ENV_NAME);	// output: TEST