npm won't get re-installed after node update

[rmoriz]

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).

[eagleeye]

same for me

Recipe: nodejs::npm_from_source
  * ark[npm] action install_with_make
    * directory[/usr/local/npm-3.8.1] action create (up to date)
    * remote_file[/var/chef/cache/npm-3.8.1.tgz] action create (up to date)
    * execute[unpack /var/chef/cache/npm-3.8.1.tgz] action nothing (skipped due to action :nothing)
    * execute[set owner on /usr/local/npm-3.8.1] action nothing (skipped due to action :nothing)
    * execute[autogen /usr/local/npm-3.8.1] action nothing (skipped due to action :nothing)
    * execute[configure /usr/local/npm-3.8.1] action nothing (skipped due to action :nothing)
    * execute[make /usr/local/npm-3.8.1] action nothing (skipped due to action :nothing)
    * execute[make install /usr/local/npm-3.8.1] action nothing (skipped due to action :nothing)
     (up to date)

[ebdrup]

we have this issue too

[bubenshchykov]

+1

[raymatos]

+1

[eagleeye]

my hotfix for this:

file '/usr/local/bin/npm' do
   action :delete
 end

 link '/usr/local/bin/npm' do
   to '/usr/local/npm-' + node['nodejs']['npm']['version'] + '/bin/npm-cli.js'
 end

[github-actions[bot]]

Marking stale due to inactivity. Remove stale label or comment or this will be closed in 7 days. Alternatively drop by the #sous-chefs channel on the Chef Community Slack and we'll be happy to help! Thanks, Sous-Chefs.

[MarkGibbons]

Part of a whole set of upgrade issues.