Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--env-file support in NODE_OPTIONS #51147

Open
afonsojramos opened this issue Dec 13, 2023 · 2 comments
Open

--env-file support in NODE_OPTIONS #51147

afonsojramos opened this issue Dec 13, 2023 · 2 comments
Labels
feature request Issues that request new features to be added to Node.js.

Comments

@afonsojramos
Copy link

What is the problem this feature will solve?

Sometimes env files are used as config files, therefore it should be allowed to set an --env-file in NODE_OPTIONS, for example in the .npmrc file, so that it applies to all scripts of that specific project.

What is the feature you are proposing to solve the problem?

Allowing for the --env-file flag to be supported in NODE_OPTIONS.

What alternatives have you considered?

No response

@afonsojramos afonsojramos added the feature request Issues that request new features to be added to Node.js. label Dec 13, 2023
@MoLow
Copy link
Member

MoLow commented Dec 13, 2023

Well, that can raise many issues and confusion since you can define NODE_OPTIONS inside the env file

@afonsojramos
Copy link
Author

I see, but I see no other solution for project specific .env, right? Do we have a way of knowing where the NODE_OPTIONS are coming from? If so, just disabling it for the .env recursive case might be a way? 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Issues that request new features to be added to Node.js.
Projects
Status: Pending Triage
Development

No branches or pull requests

2 participants