Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.


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
process: disallow adding options to process.allowedNodeEnvironmentFlags #36660
process: disallow adding options to process.allowedNodeEnvironmentFlags #36660
Changes from all commits
6262973eafaa2b466d928File filter
Conversations
Jump to
jasnellFeb 1, 2021
Member
It might seem silly but we need to at least consider whether there needs to be a deprecation cycle on this before it's made non-op.
aduh95Feb 1, 2021
Author
Contributor
Note that
process.allowedNodeEnvironmentFlags.addis already no-op on all Node.js release lines.We may or may not consider it a breaking change to make
Set.prototype.add.call(process.allowedNodeEnvironmentFlags)no-op – IMHO we should not as this never was a documented thing, but no strong feelings.