npmpackage.info

Gathering detailed insights and metrics for lazy-universal-dotenv

Other packages similar to lazy-universal-dotenv

dotenv

16.4.5

Loads environment variables from .env file

dotenv-expand

12.0.1

Expand environment variables using dotenv

universal-user-agent

7.0.2

Get a user agent string across all JavaScript Runtime Environments

dotenv-webpack

8.1.0

A simple webpack plugin to support dotenv.

Gathering detailed insights and metrics for lazy-universal-dotenv

lazy-universal-dotenv

Robust Environment Configuration for Universal Applications.

4.0.0

Apache-2.0

JavaScript

883,092,643 2.9

Installations

npm install lazy-universal-dotenv

Pull Requests

Open

0

Total

2

Closed

1

Merged

1

Issues

Open

1

Total

1

Closed

0

Releases

Unable to fetch releases

Developer

storybooks

Developer Guide

BETA

Module System

ESM

Min. Node Version

>=14.0.0

Typescript Support

No

Node Version

16.17.1

NPM Version

8.15.0 Statistics

10 Stars

81 Commits

6 Forks

4 Watching

1 Branches

97 Contributors

Updated on 15 Jun 2024

Languages

JavaScript (98.1%)

Shell (1.9%)

Total Downloads

Cumulative downloads

Total Downloads

883,092,643

Last day

-2.9%

787,992

Compared to previous day

Last week

2.6%

4,048,037

Compared to previous week

Last month

4.9%

17,316,114

Compared to previous month

Last year

3.8%

252,611,812

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

app-root-dir dotenv dotenv-expand

Dev Dependencies

jest rimraf unbuild

Versions

Lazy Universal DotEnv

Lazy Universal DotEnv - A Robust Environment Configuration for Universal Applications.

Features

Supports loading .env files with overriding between different NODE_ENV settings and BUILD_TARGET configurations.
Supports variable expansion between different settings.
Allows local overrides using files which use a ".local" postfix.

All Strings

It is important to remember that all environment variables are always stored as strings. Even numbers and booleans. The casting to other types must therefore take place in the application code. See also: https://github.com/motdotla/dotenv/issues/51

Variables

NODE_ENV: Typically either production, development or test
BUILD_TARGET: Either client or server

File Priority

Files are being loaded in this order. Values which are already set are never overwritten. Command line environment settings e.g. via cross-env always win.

.env.${BUILD_TARGET}.${NODE_ENV}.local
.env.${BUILD_TARGET}.${NODE_ENV}
.env.${BUILD_TARGET}.local
.env.${BUILD_TARGET}
.env.${NODE_ENV}.local
.env.${NODE_ENV}
.env.local
.env

Note: local files without NODE_ENV are not respected when running in NODE_ENV=test.

Basic Usage

1import { getEnvironment } from "lazy-dotenv-universal";
2
3const environment = getEnvironment({ nodeEnv, buildTarget });
4
5const { raw, stringified, webpack } = environment;

After this you can access all environment settings you have defined in one of your .env files.

A .env file:

MY_END=awesome

Webpack config:

1import { getEnvironment } from "lazy-dotenv-universal";
2
3export default {
4  // ... 
5  plugins: [
6    new webpack.DefinePlugin(getEnvironment().webpack),
7  ],
8  // ...
9}

Code being bundled by webpack:

1console.log(process.env.MY_ENV); // -> "awesome"

Serialization

raw: Just a plain JS object containing all app settings
stringified: Plain object but with JSON stringified values
webpack: For usage with Webpacks Define Plugin

License

Apache License Version 2.0, January 2004

Copyright

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

License

Determines if the project has defined a license.

4

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Maintained

Determines if the project is "actively maintained".

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

Security-Policy

Determines if the project has published a security policy.

0

SAST

Determines if the project uses static code analysis.

Score

2.9

/10

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