webpack / webpack/enhanced-resolve
Support `node:http` etc.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 983
- Forks
- 206
- Avg merge
- 23h 27m
- Merged PRs (30d)
- 15
Description
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 with the linked Node.js ESM documentation and the is-builtin-module workaround, then trace enhanced-resolve's resolver entry points for how built-in module names are handled. Done should mean node:http and similar node: imports resolve correctly, with relevant tests updated or added.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100