-
Notifications
You must be signed in to change notification settings - Fork 50
NPM executables not symlinked #94
Comments
I'm not sure what you wanna say ... nodejs v0.12.2 is delivered with npm 2.7.4 - see /usr/local/node/node-v0.12.2/lib/node_modules/npm/package.json There is a symlink /usr/local/node/node-v0.12.2/bin/npm -> ../lib/node_modules/npm/bin/npm Using the class { 'nodejs':
version => 'stable',
} there are symlinks of /usr/local/bin/node -> /usr/local/node/node-default/bin/node and /usr/local/bin/npm to /usr/local/node/node-default/bin/npm Using the define: nodejs::install { 'v0.12.2':
version => 'v0.12.2',
} there are symlinks under /usr/local/bin including the node release number |
This is what I get on Ubuntu 14.04 server
|
for which manifest? |
I have this same issue. No symlink for npm, just node. ll /usr/local/bin/ | grep node The path IS on the nodejs user's path, but Puppet runs as root of course, so the PM2 module which includes this cannot execute npm |
I also have the same issue. I actually specified target_dir => '/usr/bin' and there are a couple of things missing:
|
It is possible that the problem occurs when installing from pre-built package with |
ok, could be reproduced. WHen installing Node 5 and Node 0.12 on a VM the following node executables are available globally:
But only one global npm executable (3.x which is shipped with node 5) is available. |
due to some weird internals of npm this bug is a bit harder to solve, so it may take a bit more time. |
sorry, I have to close this as "can't fix". This is connected with a few issues:
When trying to solve that, we would mess up the code for a case where no solutions are provided from the node side. |
we have to fix the documentation |
in 2.0 it should be possible to fix this finally |
…right nodejs executable (#153) - create templates which map the NPM executable to the corresponding NodeJS instance
Hello all,
When I do:
Without master nodejs install with:
on Ubuntu 14.04 the instal of node was OK and the symlink of /usr/local/bin in ok too:
But there is no npm-v0.12.2 in there ....
Is this expected or is it a bug...
The text was updated successfully, but these errors were encountered: