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

dotenv-placeholder

v1.7.1

Published

This package is a wrapper for [`dotenv`](https://www.npmjs.com/package/dotenv) to make it work with Git more easily

Downloads

6

Readme

.env + .env.placeholder

This package is a wrapper for dotenv to make it work with Git more easily

It makes your life easier with your git repository if you decide to add .env to the .gitignore of your project (very good decision by the way, that's the way it should be)

What does it do ?

If no .env.placeholder file is found, it will create one next to your .env file, and will put the keys indicated in your .env file, without the values.

If no .env file is found, it will create one next to your .env.placeholder file, and will copy in it the content found in .env.placeholder

It warns you if you have empty fields in .env

You can add default values to the .env.placeholder and it will add this values to the .env file EXCEPTED if there is already a value given in .env for this key

You can add a <random:♥> value in .env.placeholder (where represents the length of the random string you want to generate), or just <random>, which is equivalent to <random:30>.

Example

# .env
KEY=secret_value

# .env.placeholder
ADDITIONAL_KEY=
KEY_WITH_DEFAULT=default_value
A_RANDOM_KEY=<random>

Will transform into :

# .env
KEY=secret_value
ADDITIONAL_KEY=
KEY_WITH_DEFAULT=default_value
A_RANDOM_KEY=k7RDE_aBJxAE==qchk720DH-4Rzc

# .env.placeholder
ADDITIONAL_KEY=
KEY_WITH_DEFAULT=default_value
A_RANDOM_KEY=<random:28>
KEY=

And it will produce the following messages in the console :

info .env.placeholder → .env :  [ 'ADDITIONAL_KEY', 'KEY_WITH_DEFAULT', 'A_RANDOM_KEY' ]
info .env.placeholder ← .env :  [ 'KEY' ]
warning empty keys found in .env : [ 'ADDITIONAL_KEY' ]

How to use it

In your Node.js script

const dotenv = require("dotenv-placeholder");
dotenv.config(); // this will trigger the build

In your package.json

This is my prefered way, because when someone will clone your project, and then run npm i, it will automatically create the .env file, allowing the person to customize the .env before running your project

{
    "scripts": {
        "postinstall": "dotenv-build --path=./config/.env --placeholderPath=./config/.env.placeholder"
        /* all options are optionnal */
    }
}