Improve the performance of both URLSearchParams.toString and querystring.stringify
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Shell
- Stars
- 399
- Forks
- 11
- Avg merge
- 29m
- Merged PRs (30d)
- 1
Description
Fast-querystring is almost 2x faster for stringifying. Let's copy my code (which is MIT) to Node.js
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 reviewing the fast-querystring implementation linked in the issue, then locate Node.js's URLSearchParams.toString and querystring.stringify implementations. Compare their behavior and measure the existing performance before determining whether the copied implementation improves both stringification paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100