-
-
Notifications
You must be signed in to change notification settings - Fork 35.6k
.env file support issue tracker #49148
Copy link
Copy link
Open
Labels
discussIssues opened for discussions and feedbacks.Issues opened for discussions and feedbacks.dotenvIssues and PRs related to .env file parsingIssues and PRs related to .env file parsing
Metadata
Metadata
Assignees
Labels
discussIssues opened for discussions and feedbacks.Issues opened for discussions and feedbacks.dotenvIssues and PRs related to .env file parsingIssues and PRs related to .env file parsing
Type
Fields
Give feedbackNo fields configured for issues without a type.
This is a follow-up of dotenv support pr to track the development process, and answer some questions that require a general discussion for making the decision to implement them.
Todos:
.envfiles, and consider a better format not based on ini--env-filethrough the CLI? (cc @GeoffreyBooth) src: support multiple--env-filedeclarations #49542UV_THREADPOOL_SIZEtests on.env#49213process.loadEnvFileandutil.parseEnv#51476Questions:
Should we merge NODE_OPTIONS if both environment variable and .env version exist? Currently, we prefer environment variable over .env configuration.(cc @ljharb) src: merge env-file and env vars ofNODE_OPTIONS#49217.envfile does not exist? We currently follow the default behavior ofdotenvpackage and do not throw. (cc @MoLow)Please feel free to edit this issue in case there are more questions that needs to be answered.
cc @nodejs/tsc