56
loading...
dotenv Module for managing runtime environments
Dotenv is a zero-dependency module that loads environment variables from a .env file into process.env. Storing configuration in the environment separate from code is based on The Twelve-Factor App methodology.
Dotenv Module will help us to populate runtime configuration during runtime, like populating mysql connection details while starting up mysql connection with nodejs, or providing mongodb connection url while starting application
Its minimal configuration we just need to have .env file in root of the application and
Its minimal configuration we just need to have .env file in root of the application and
require('dotenv').config() it will populate all .env variables in process.env objectSo all required configuration gets populated to process.env and application runs as expected.
Environment variables are supported out of the box with Node and are accessible via the env object (which is a property of the process global object.)
To see this in action, you can create your own environment variable right in the Node REPL by appending a variable to the process.env object directly.
To see this in action, you can create your own environment variable right in the Node REPL by appending a variable to the process.env object directly.
For example, you can create a simple env variable like process.env.LUGGAGE_COMBO=“12345”.
Here we have added LUGGAGE_COMBO to env object in process now this variable can be accessed by node js process
Here we have added LUGGAGE_COMBO to env object in process now this variable can be accessed by node js process
# with npm
npm install dotenv
# or with Yarn
yarn add dotenvUsage
As early as possible in your application, require and configure dotenv.
As early as possible in your application, require and configure dotenv.
require('dotenv').config()Create a .env file in the root directory of your project. Add environment-specific variables on new lines in the form of NAME=VALUE. For example:
DB_HOST=localhost
DB_USER=root
DB_PASS=s1mpl3process.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
})always keep .env.example or env.dist, env.test files to just explain what all variables application will need, never commit original .env file put this in .gitignore
This is another helpful module which can help us to pass different configuration for dev and test
Example lets say we have .env and .env.test files and for running tests we want to pass test configurations in code so using NPM scripts we can pass test configurations and tests will run on test database configuration
Example lets say we have .env and .env.test files and for running tests we want to pass test configurations in code so using NPM scripts we can pass test configurations and tests will run on test database configuration
"test:unit": "dotenv -e .env.testing -- npm run test:unit",
"test:e2e": "dotenv -e .env.testing -- npm run test:e2e",NPM
$ npm install -g dotenv-cliYarn
$ yarn global add dotenv-cli$ dotenv <command with arguments>This will load the variables from the .env file in the current working directory and then run the command (using the new set of environment variables).
Another .env file could be specified using the -e flag:
$ dotenv -e .env2 <command with arguments>Multiple .env files can be specified, and will be processed in order:
$ dotenv -e .env3 -e .env4 <command with arguments>Reference Links
Conclusion:
Now using dotenv-cli i can pass different runtime configurations in NPM Scripts
To know more about what is environment variables you can checkout this blog
https://medium.com/chingu/an-introduction-to-environment-variables-and-how-to-use-them-f602f66d15fa
https://medium.com/chingu/an-introduction-to-environment-variables-and-how-to-use-them-f602f66d15fa
56