Explicitly set npm install folder #96
Merged
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.
Summary
Explicitly set the folder for
npminstall in using the--prefixflag to prevent installation into the wrong folder.Reason for change
In the current
install_npm_depsscript, wecdinto theassetsfolder then perform the installation. This won't always work because if apackage.jsondoes not already exist in theassetsfolder,npmwill look for the nearest parent folder containing either apackage.jsonfile or anode_modulesfolder and do the installation there.Using the
--prefixflag will force installation in the specified folder.