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

dev-tool-envdist

v1.0.30

Published

Envdist - is CLI tool for generation .env files from '.env.dist.'

Downloads

2

Readme

Envdist

What is it?

Envdist - is CLI tool for generation .env files from .env.dist.

CLI Interface envdist [environment] [flag].

Installation

$ npm i -g envdist

or

$ npm i -D envdist

You can set the package as global or dev dependency

Place | Command | Usage example :--- | :--- | :--- Global | npm i -g envdist | $ envdist Dev | npm i -D envdist | $ npx envdist $ ./node_modules/.bin/envdist

Usage

Base usage

Create .env.dist file. For example.

#Application settings

NODE_ENV = <Environment>  # development
PORT = <Application port> # 3000

Execute

For manually enter (the environment is defined automatically from the NODE_ENV variable):

$ envdist

For manually enter variables of development environment:

$ envdist development

Generate file from environment variables (suitable for use in deploy or runnig CI/CD):

$ envdist production -e

Force generation (Sets default values else trying fetch from environment variables else set empty value):

$ envdist development -f

Override existing values:

$ envdist development -o

Resolve environment variables:

$ envdist development -r

Configuration

Insert this config to package.json.

  "env": {
    "path": ".",
    "dist": ".env.dist",
    "pattern": ".env",
    "strategies": {
      "manual": ["", "dev"],
      "variables": ["prod", "stage", "test"]
    }
  }

Options

Option | Description :--- | :--- path | Path to your env.dist file. For example './env'. Default: '.'. dist | Dist file name. If you have many dist files then you can use pattern '*.env.dist'. For environment test dist file will be test.env.dist. Default: '.env.dist'. pattern | Pattern for output .env files. You can usage pattern as in dist option. Default: '.env'. strategies | This parameter contains the manual and variables properties to declare the default strategy using the NODE_ENV variable.manual equal run envdist [ENV] or envdist [ENV] -m.variables equal run envdist [ENV] -e

Auto creation .env files after installation packages NPM

Just add to your package.json next script

{
  "scripts": {
    "install": "npx envdist"
  }
}

Triggered on npm install or npm i.

Enjoy!