This repository has been archived by the owner on Jan 15, 2024. It is now read-only.
create version-aware executables to provide multiple npm installations #112
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
/cc @willdurand not sure whether that's a bit too hacky. Could you please have a look at that? |
|
|
||
| file { $npm_filename: | ||
| ensure => file, | ||
| mode => 0777, |
There was a problem hiding this comment.
filemode should be quoted
| # the version will be extracted from the CLI. | ||
| # the output contains a line break, but this line break causes weird | ||
| # symlink names, so the version needs to be stripped. | ||
| version.strip |
There was a problem hiding this comment.
the v- prefix is missing
|
see ticket #94 for more information |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
this is not related to #83 .
resolves #94
The issue is that when having multiple node instances in a VM, there are multiple executables (node-v5.4.1, node-v0.12.2, etc.), but not multiple npm executables.
This is because of the fact that npm's executable always calls the "node" executable, but this means that even npm 2 would work with node 5 and not with node 0.12 although npm 2 has been installed with npm 0.12.
The fix for that issue was to create executables like "npm-2.7.4", etc., but those call inside the proper "npm" callable, but with the proper npm executable, so it is possible execute the proper executable with the proper node environment.