Request: Omitting experimental flags from new config file
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
Opening this issue on behalf of several individuals with whom I spoke about the new configuration file landed in https://github.com/nodejs/node/pull/57016 ...
The specific request from three separate people in separate conversations is to specifically omit --experimental-* flags from the configuration file format, even if hose flags are otherwise allowed in NODE_OPTIONS.
/cc @marco-ippolito @ljharb @ShogunPanda @anonrig @joyeecheung @mhdawson @bnb (as the folks who authored/reviewed that PR)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading pull request 57016 and the new configuration file format, then compare its handling with the existing NODE_OPTIONS behavior. Determine how experimental flags are identified and confirm the expected result with the issue discussion: --experimental-* flags should be omitted from the configuration file even when allowed in NODE_OPTIONS.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100