TextDecode Regression
Open
Nobody has claimed this yet.
benchmark-needed
- Dominant language
- Shell
- Stars
- 399
- Forks
- 11
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
TextDecoder.decode() has drastically regressed in Node.js 22 (in comparisson to with Node.js 20)
Refs: https://nodesource.com/blog/State-of-Nodejs-Performance-2024
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 reproducing the TextDecoder.decode() comparison described in the issue with Node.js 20 and Node.js 22, using the linked performance reference for context. Determine which benchmark or reproduction is represented by the screenshot; done means the regression is isolated and the issue has a confirmed, repeatable result or a clearly documented next step.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100