env-path

Loads environment variables from a chosen .env file into process.env, using dotenv and dotenv-expand

> Adds .env variables to process.env

``sh
package.json
"scripts": {
"test" : "env-path -p path/.env node app.js"
"build" : "env-path -p path/.env.production, react-scripts build"
"start" : "env-path -p otherPath/.env-file react-script start",
}
`

Installation


![NPM version](https://www.npmjs.com/package/env-path)
`sh
$ npm install env-path
`

Usage

Thanks to dotenv-expand, we can use variables inside our .env file.

See simple .env file under


`sh
API_KEY=key
PORT=3000
MONGO_DB=myDB
MONGO_URL=mongodb://localhost:27017/${MONGO_DB}
REACT_APP_VERSION=$npm_package_version
`




$3


Preloads dotenv and dotenv-expand. By doing this, you do not need to require and load dotenv and dotenv-expand in your application code.
#### Path
Specify a path using the -p flag:

>$ env-path -p path/.env-file node app.js


`sh
package.json
"scripts": {
"build" : "env-path -p path/.env.production, react-scripts build"
"start" : "env-path -p path/.env-file react-script start",
"start2" : "env-path -p path/.env.development node app.js",
"start3" : "env-path -p path/otherFileName.env node app.js",
}
`

#### Without path

Works similar to dotenv's Preload

See dotenv docs

>$ env-path node app.js

`sh
package.json
"scripts": {
"start" : "env-path node app.js",
"build" : "env-path react-scripts build"
}
``

License

MIT