Don't cache HTTP errors in the module map
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
The current spec behavior doesn't allow developers to retry failed module imports, as the failure result (either an HTTP error or a network failure) gets cached.
https://github.com/whatwg/html/pull/10327 fixes that. Browsers/runtime environments should implement that change.
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 the WHATWG HTML pull request 10327 and compare its module-map behavior with Node.js's module loading implementation. Trace how failed HTTP and network imports are cached, then verify that retrying those imports succeeds after the change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100