Benchmark npm ci
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 433
- Forks
- 28
- Avg merge
- 48m
- Merged PRs (30d)
- 6
Description
In npm v5.7.1 a new command was added - npm ci. Npm team claims it is faster (2x-10x) than npm install
The new npm ci command installs from your lock-file ONLY. If your package.json and your lock-file are out of sync then it will report an error.
It works by throwing away your node_modules and recreating it from scratch.
Beyond guaranteeing you that you'll only get what is in your lock-file it's also much faster (2x-10x!) than npm install when you don't start with a node_modules.
As you may take from the name, we expect it to be a big boon to continuous integration environments. We also expect that folks who do production deploys from git tags will see major gains.
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
The issue names npm ci but provides no repository file, test, or benchmark entry point. Start by locating the existing package-manager benchmark setup, then run the npm ci comparison against npm install and record results showing whether the claimed speed difference is reproduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance, tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100