Benchmark doesn't check native modules.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 433
- Forks
- 28
- Avg merge
- 48m
- Merged PRs (30d)
- 6
Description
Your benchmark doesn't packages which require native compilation.
Try to depend on truffle, for example. it depends on quite a few native modules.
NPM compiles them one by one. Yarn opens multiple parallel processes to compile, and achieves great efficiency.
Moreover, since re-install often requires to compile such native modules again (I don't really know why, but both NPM and Yarn do it) , the above compilation times affect not only initial installs but also re-installs.
Contributor guide
No contributing guide indexed for this repository
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 existing benchmark cases and how they install packages, then compare the npm and Yarn behavior described in the issue using truffle as a dependency. Done means the benchmark includes native-module compilation for both initial installs and reinstalls, with the results recorded for comparison.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devtools, performance
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100