Gathering detailed insights and metrics for dotenv-with-expand
Gathering detailed insights and metrics for dotenv-with-expand
Gathering detailed insights and metrics for dotenv-with-expand
Gathering detailed insights and metrics for dotenv-with-expand
npm install dotenv-with-expand
Module System
Min. Node Version
Typescript Support
Node Version
NPM Version
9 Stars
12 Commits
4 Forks
4 Watching
1 Branches
3 Contributors
Updated on 17 Oct 2023
JavaScript (100%)
Cumulative downloads
Total Downloads
Last day
66.1%
103
Compared to previous day
Last week
-21.4%
302
Compared to previous week
Last month
-7.5%
1,270
Compared to previous month
Last year
-7.3%
15,959
Compared to previous year
2
DEPRECATION NOTICE
Support for .env
file is now a builtin feature of Node.js.
See https://nodejs.org/en/blog/release/v20.6.0#built-in-env-file-support
This is a drop-in replacement for dotenv but with preloaded dotenv-expand functionality.
1# with npm 2npm install dotenv-with-expand 3 4# or with Yarn 5yarn add dotenv-with-expand 6 7# or with pnpm 8pnpm install dotenv-with-expand
As early as possible in your application, require and configure dotenv.
1require('dotenv-with-expand').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:
1DB_HOST=localhost 2DB_USER=root 3DB_PASS=s1mpl3 4DB_URI="${DB_USER}:${DB_PASS}@${DB_HOST}"
process.env
now has the keys and values you defined in your .env
file.
See dotenv-expand for more substitution examples.
1const db = require('db'); 2db.connect({ 3 host: process.env.DB_HOST, 4 username: process.env.DB_USER, 5 password: process.env.DB_PASS, 6}); 7console.log(`connected to ${process.env.DB_URI}`);
You can use the --require
(-r
) command line option to preload dotenv. By doing this, you do not need to require and load dotenv in your application code. This is the preferred approach when using import
instead of require
.
1$ node -r dotenv-with-expand/config your_script.js
The configuration options below are supported as command line arguments in the format dotenv_config_<option>=value
1$ node -r dotenv-with-expand/config your_script.js dotenv_config_path=/custom/path/to/your/env/vars
Additionally, you can use environment variables to set configuration options. Command line arguments will precede these.
1$ DOTENV_CONFIG_<OPTION>=value node -r dotenv-with-expand/config your_script.js
1$ DOTENV_CONFIG_ENCODING=latin1 node -r dotenv-with-expand/config your_script.js dotenv_config_path=/custom/path/to/.env
config
will read your .env
file, parse the contents, assign it to
process.env
,
and return an Object with a parsed
key containing the loaded content or an error
key if it failed.
Please refer to dotenv for more information.
The engine which parses the contents of your file containing environment variables is available to use. It accepts a String or Buffer and will return an Object with the parsed keys and values.
Please refer to dotenv for more information.
Please refer to dotenv for more information.
No vulnerabilities found.
Reason
no binaries found in the repo
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
SAST tool detected but not run on all commits
Details
Reason
Found 1/6 approved changesets -- score normalized to 1
Reason
project is archived
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
project is not fuzzed
Details
Reason
security policy file not detected
Details
Reason
branch protection not enabled on development/release branches
Details
Score
Last Scanned on 2024-11-18
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More