sous-chefs/nodejs

npm won't get re-installed after node update

Open

#120 opened on Mar 10, 2016

View on GitHub
 (7 comments) (1 reaction) (0 assignees)Ruby (188 forks)auto 404
BugHelp WantedMaintenancePriority: Mediumhacktoberfest

Repository metrics

Stars
 (228 stars)
PR merge metrics
 (PR metrics pending)

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

Research direction
Inspect the cookbook's recipe for npm installation. The issue suggests the recipe only checks if the npm directory exists, not the npm version. Trace the logic to understand how node and npm are installed, and identify where a version check should be added to trigger reinstallation when npm is outdated.
Tech stack
ruby
Domain
devopsinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ChefRuby
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65