Comments (2)
Hi @viveksharmaui,
You don't need to have the original dotenv
package, because it's already a dependency of dotenv-flow
.
The following just should work fine:
import dotenvFlow from 'dotenv-flow';
dotenvFlow.config();
Also, note that exporting the dotenvFlow
is redundant, because when you call .config()
it fills out process.env
which is global.
--
As for the NODE_ENV
environment variable, it shouldn't be placed in any .env
file. This environment variable controls which of the .env
file will be loaded.
For example, if you run your script like:
$ NODE_ENV=production node your_script.js
it will load environment variables from .env
(the default) and .env.production
(node_env-specific).
If you run your script like:
$ NODE_ENV=development node your_script.js
it will load environment variables from .env
and .env.development
.
But if you run your script without specifying NODE_ENV
, like:
$ node your_script.js
it will only load the .env
file (the default one).
--
You can also define the default NODE_ENV
to load .env
and .env.development
by default, like:
import dotenvFlow from 'dotenv-flow';
process.env.NODE_ENV = process.env.NODE_ENV || 'development';
dotenvFlow.config();
from dotenv-flow.
Closed #18
from dotenv-flow.
Related Issues (20)
- node your_script.js --node-env=production does not work HOT 1
- Specifying NODE_ENV in .env.local file HOT 3
- cli executable HOT 6
- Suggestion: schema file HOT 1
- Why items in .env.local is not picked ? HOT 2
- Is this the 12 factor way? HOT 2
- no default export.ts HOT 1
- no error property set when .env file is not present HOT 3
- Empty values aren't respected HOT 2
- Ability to change `NODE_ENV` option to switch .env.<NODE_ENV> files HOT 2
- cannot use base64 encoded .env file to decode HOT 2
- Error with symlink .env.local HOT 1
- config({purge_dotenv=true}) fails to load any environment if .env not found HOT 1
- Is DOTENV_FLOW_SILENT supposed to suppress "already defined" messages? HOT 8
- how to load with import? HOT 9
- Is this package still maintained? HOT 9
- Launch "test:e2e": "vue-cli-service test:e2e --mode e2e" , but only .env is loaded HOT 1
- bug(load): Non-existent files fail silently HOT 4
- npx mocha -r dotenv-flow/config --recursive app not working on 4.0.0 but was fine on 3.2.0 HOT 1
- variables overwriting/priority does not match Next.js HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dotenv-flow.