nuxt-community/dotenv-module

System vars should overwrite dotenv vars

Open

#46 opened on Oct 15, 2019

View on GitHub
 (9 comments) (3 reactions) (0 assignees)JavaScript (482 stars) (32 forks)batch import
cmty:feature-requesthelp wanted

Description

What problem does this feature solve?

In most places where dotenv is used system env vars override the dotenv vars, however dotenv-module does the exact opposite, swapping this around would give the expected result when using systemvars: true

Contributor guide

Tech stack
javascriptnodejs
Domain
backend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic Node.js knowledgeFamiliarity with dotenv
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85
Research direction
Investigate the dotenv module source code to find where environment variables are loaded and the merging logic. The issue is in the module's core file (likely `lib/module.js` or similar) where `process.env` and dotenv parsed values are combined. The fix is to ensure that system environment variables take precedence over dotenv values when `systemvars: true` is set. Review the existing tests and add a test case for this behavior.
System vars should overwrite dotenv vars · nuxt-community/dotenv-module#46 | Good First Issue