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

autoenv

v1.0.12

Published

automatically load dotenv files based on NODE_ENV

Downloads

50

Readme

AutoENV

automatically load dotenv files based on NODE_ENV

license release semantic

autoenv uses dotenv to automatically load environment variables from a compatible .env file into process.env.

Install

npm install autoenv

Config

Create a default .env file in the root directory of your project.

DB_HOST=localhost
DB_USER=root
DB_PASS=s1mpl3

Create additional .env.xyz files matching as many environment variants you want:

my_project/
├── .env
├── .env.development
├── .env.staging
└── .env.production

The default .env will always be loaded, if a matching .env.${NODE_ENV} file is present, it will be loaded and overrides the values in .env

Usage

As early as possible in your application, require and configure dotenv.

require('autoenv')

When starting your application, ensure NODE_ENV is set to the environment name you wish to load.

NODE_ENV=staging node index.js
export NODE_ENV=staging
node index.js

Preload

You can use the --require (-r) command line option to preload autoenv. By doing this, you do not need to require in your application code.

node -r autoenv index.js

That's it.

process.env now has the keys and values you defined in your .env file.

const db = require('db')
db.connect({
  host: process.env.DB_HOST,
  username: process.env.DB_USER,
  password: process.env.DB_PASS
})

Author: Ahmad Nassri • Twitter: @AhmadNassri