fs: utf8 fast paths don't accept all valid utf8 values
Open
Nobody has claimed this yet.
fs
- Dominant language
- JavaScript
- Stars
- 122k
- Forks
- 37.3k
- Avg merge
- 4d 2h
- Merged PRs (30d)
- 283
Description
UTF8 and UTF-8 are also valid but not accepted by any existing utf8 fast paths (#48658, #49884)
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 tracing Node.js fs UTF-8 fast paths and compare their handling of utf8, UTF8, and UTF-8, using issues #48658 and #49884 for context. Check the existing fs tests covering encoding aliases; done means all valid spellings are accepted consistently by the fast paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100