Node ecosystem might need to preserve using `file:` protocol
Open
Nobody has claimed this yet.
feature request
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
Various things in the ecosystem use symlinks, the behavior of symlinks in node and how HTTP redirects is not compatible per https://github.com/nodejs/modules/issues/62 . Could repurpose the Location header over file: but https://fetch.spec.whatwg.org/#scheme-fetch could be changed in a forwards incompatible way if we do that.
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 Node modules issue #62 and the Fetch Standard's scheme-fetch section referenced here. Trace how symlinks, HTTP redirects, and the file: protocol interact, then establish the compatibility requirements; done means a concrete, reviewed direction for preserving the Node ecosystem's behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100