This repository was archived by the owner on Nov 10, 2022. It is now read-only.
Ignore node_modules
symlinks when installing npm
.
#177
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.
Having symbolic link to
node_modules
in the project root (as e.g. in case of a client's plugins using globalnode_modules
via symlink) generates Travis error:After removing
node_modules
symlinks in plugins, builds are okay.However, having symlink in plugin's directory facilitates development, so it's not a best idea to remove them completely. In this case, I've modified
check-diff.sh
script to go ahead and ignore symlink. This waynpm
should be installed in each Travis build.I'm open to any developer having a look and commenting/merging this into
master
.@westonruter - I'm assigning this to you primarily, as you already saw my struggles with this issue.