Loads environment variables from .env

npm install dotenv
62 downloads in the last day
874 downloads in the last week
3 692 downloads in the last month


Dotenv loads environment variables from .env into ENV (process.env). It is a superior alternative to nconf and other variants.

BuildStatus NPM version

"Storing configuration in the environment is one of the tenets of a twelve-factor app. Anything that is likely to change between deployment environments–such as resource handles for databases or credentials for external services–should be extracted from the code into environment variables.

But it is not always practical to set environment variables on development machines or continuous integration servers where multiple projects are run. Dotenv load variables from a .env file into ENV when the environment is bootstrapped."

Brandon Keepers' Dotenv in Ruby


Add it to your package.json file.

  "dependencies": {
    "dotenv": "0.2.8"


As early as possible in your application require dotenv and load the .env variables:

var dotenv = require('dotenv');

Then, create a .env file in the root directory of your project. Add the application configuration you want. For example:


Whenever your application loads, these variables will be available in process.env:

var sendgrid_username = process.env.SENDGRID_USERNAME;
var secret_key        = process.env.SECRET_KEY;

That's it. You're done.


Also added in 0.2.6 the method parse has been exposed. This is how dotenv internally parses multiline buffers or strings into an object to place into the process.env object.

var dotenv  = require('dotenv');
var file    = fs.readFileSync('./config/staging');
var config  = dotenv.parse(file); // passing in a buffer
console.log( typeof config, config ) // object { API : '' }

Should I commit my .env file?

Try not to commit your .env file to version control. It is best to keep it local to your machine and local on any machine you deploy to. Keep production credential .envs on your production machines, and keep development .envs on your local machine.


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

Running tests

npm install
npm test

Who's using dotenv

Here's a list of apps/sites/libraries using dotenv. It's in no way a complete list.

Create a pull request and add yours to the list.

npm loves you