Node: install latest version of npm
- Dominant language
- HTML
- Stars
- 57
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
Developers are often getting unexpected changes in their `package-lock.json` when running `npm install` in their project. This is most of the time caused by developers using different major versions of npm.
To avoid this as much as possible, we should probably enforce the update of npm to the lastest version during the provisioning.
Contributor guide
Research direction
The issue does not name a file, test, or provisioning entry point. Start by locating the Ansible provisioning code that installs Node and npm, then determine how the latest npm version should be enforced during provisioning. Done means provisioning consistently updates npm and no longer leaves developers on differing major versions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, node.js
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100