Those are warnings, whats the full output?

That’s the full output - I can’t see anymore ? :/

@nuborian

Have you tried running npm update? If not, try running that and running the install again.

If the issue persists, or if only some of the warnings persist, try installing the packages noted and upgrading the one that needs to be.

i.e.

npm install -g minimatch@3.0.2 \
&& npm install -g uuid \
&& npm install -g any-promise

Thanks for your help - sadly that doesn’t work, too :/

For anyone running into this issue. It seems to be due to running out of memory on the smaller Droplets. I temporarily resized to a 2GB droplet and Sails installed fine. I was monitoring memory usage and about 2/3 of the way through the install it was bumping up on 500MB of ram used. Near the end of the install it exceeded the 512MB of ram on the smallest droplet size.

@cshepcook @nuborian @jtittle @Woet Hey everyone, for future reference, the issue is probably pre-production Grunt compilation running on Digital Ocean (which is relatively memory-intensive, depending on the number of assets you have). An easy workaround for this is to prepare (e.g. compile/minify/etc) production assets ahead of time (locally on your machine, before deploying).

For a tip on how to prepare assets ahead of time, check out https://github.com/balderdashy/sails/issues/3577#issuecomment-184786535 (you don’t actually need to name the task “cluster”– e.g. you might name it “digitalocean” or “preproduction”).

Hope that helps!
-mikermcneil