Fix errors and slowness during grunt-sass install process #1246
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.
Fixes #1212 and in the process significantly improves the runtime and performance of
vagrant up
(a fresh install now runs about 10-15 minutes faster for me).Removing the
&> /dev/null
fromnpm install grunt-sass
reveals a pretty nasty issue. It starts like this:then,
node-gyp
kicks in with its own errors:This same error message repeats, quickly reaching millions of log lines, until
node-gyp
runs out of memory:Then the installation continues. Currently, all of this is hidden from the user, but towards the end of this
node-gyp
process, it's not possible tovagrant ssh
into the VM because free memory is so low.The fix here is not particularly elegant, but it's the only thing I've found that works, and I think the current state of things is much worse. See npm/npm#3849 (comment) and npm/npm#601 for some background.