sous-chefs / sous-chefs/nodejs
npm won't get re-installed after node update
Open
Nobody has claimed this yet.
Bug
hacktoberfest
Help Wanted
Maintenance
Priority: Medium
- Dominant language
- Ruby
- Stars
- 228
- Forks
- 186
- Avg merge
- 5h 45m
- Merged PRs (30d)
- 1
Description
Given:
- node installed using binary method
- npm installed using source method
When:
- update node version
- leave npm version unchanged
Then
- embbed npm of node is used.
npm recipe should check the current npm version and re-install if is below the version specified in attributes. Ark only checks if the directory already exists (eg /usr/local/node-3.8.0).
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 the npm recipe and its attributes, focusing on how it checks the existing directory such as /usr/local/node-3.8.0. Reproduce the binary Node/source npm setup described in the issue, then verify that the current npm version is compared with the configured version and that an older version is re-installed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, ruby
- Domain
- devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100