Should we start testing npm@12?
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 86/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- javascript
- Domain
- ci-cd
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.
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
- Dominant language
- Python
- Stars
- 155
- Forks
- 101
- Avg merge
- 6d 2h
- Merged PRs (30d)
- 4
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.
More from nodejs/gyp-next
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
-
github_actions question
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
[typo] miss < Open
Difficulty 1/5 Under an hour Newbie friendliness 45/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100