refactor: Use node:
protocol for built-in Node.js modules
#18434
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prerequisites checklist
What is the purpose of this pull request? (put an "X" next to an item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:
Updates all modules to use
node:
protocol when requiring built-in Node.js modules.What changes did you make? (Give an overview)
n/prefer-node-protocol
rule and let it autofix the whole project.node:
.Is there anything you'd like reviewers to focus on?
When testing whether the new
@eslint/config-array
package will work when used from eslint, I noticed that the webpack build (part of the browser test) fails with:So, the first goal was to make the browser test (and eventually the Playground build on eslint.org) work. Then I switched to
node:
in a few places in eslint to additionally test the build, and in the end I decided to switch tonode:
in the entire project.