UTF8 and UTF-8 are also valid but not accepted by any existing utf8 fast paths (#48658, #49884)
Contributor guide
Tech stack
nodejsjavascriptcpp
Domain
backendperformance
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
understanding of UTF 8 encodingfamiliarity with Node.js file system internalsbasic C++ debugging skills
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Investigate the existing utf8 fast paths in Node.js's fs module (likely in lib/internal/fs/utils.js or src/node file.cc). Examine issues #48658 and #49884 for context. Determine where UTF8 and UTF 8 strings are compared and make the comparison case insensitive or add the accepted variants. Ensure consistency with the encoding normalization function. Add tests for the new accepted values.
