Gathering detailed insights and metrics for @dragon-syndicate/dotenv-mono
Gathering detailed insights and metrics for @dragon-syndicate/dotenv-mono
Gathering detailed insights and metrics for @dragon-syndicate/dotenv-mono
Gathering detailed insights and metrics for @dragon-syndicate/dotenv-mono
npm install @dragon-syndicate/dotenv-mono
Typescript
Module System
Node Version
NPM Version
63.4
Supply Chain
85.1
Quality
81.8
Maintenance
100
Vulnerability
80.9
License
Built with Next.js • Fully responsive • SEO optimized • Open source ready
Total Downloads
1,136
Last Day
1
Last Week
13
Last Month
40
Last Year
1,136
Latest Version
1.2.1
Package Id
@dragon-syndicate/dotenv-mono@1.2.1
Unpacked Size
236.25 kB
Size
75.93 kB
File Count
7
NPM Version
10.8.2
Node Version
20.17.0
Published on
Oct 10, 2024
Cumulative downloads
Total Downloads
Last Day
0%
1
Compared to previous day
Last Week
333.3%
13
Compared to previous week
Last Month
1,233.3%
40
Compared to previous month
Last Year
0%
1,136
Compared to previous year
Environment variables are loaded from multiple folders, starting with the current working directory (cwd) and moving up the directory tree until the max depth is reached. The root directory is considered to be the directory at the top of the directory tree, based on the max depth. The environment variables will be loaded starting with the .env
files in the root directory and then moving down the directory tree until the cwd is reached.
Variables are processed from the .env
file into Environment variables based on when they are loaded. Variable interpolation is supported for all variables loaded from the .env
files. If a variable has not already been loaded into the Environment variables and is referenced using interpolation, it will result in an empty string.
A variable defined in multiple .env
files will be overwritten by the last .env
file that is loaded. This means that the .env
file in the cwd will overwrite any variables that are defined in the .env
files in the parent directories.
ENV
and an extension can be added to the .env
files to load additional variables based on the extension. The .env
files are loaded in the following order in each directory:
.env
.env.local
.env.<ENV>
.env.<ENV>.local
.env.<extension>
.env.<extension>.local
.env.<extension>.<ENV>
.env.<extension>.<ENV>.local
dist
folder to be published to npmjs
1pnpm run dev
1pnpm run test
1pnpm run build
1pnpm run clean
To locally test the release process you will need to run the command in the root directory cd dist && npx semantic-release --dry-run
.
NOTE: This command will only work if you have already logged in to npmjs via the command npm login
.
No vulnerabilities found.