Should we start testing npm@12?
Open
Beginner friendly
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 155
- Forks
- 101
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 4
Description
Will currently install npm@11, so should we try to install npm@12 over it globally to ensure that there are no breaking changes?
- run: npm install --global npm@12
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 with .github/workflows/node-gyp.yml at the linked line and inspect how npm@11 is installed in the workflow. Update the version used for the check, then run the workflow to confirm npm@12 installs successfully and introduces no breaking changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 86/100