Curious why seed is caching node_modules folder in...
# seed
d
Curious why seed is caching node_modules folder instead of caching `~/.npm`https://stackoverflow.com/questions/42521884/should-i-have-travis-cache-node-modules-or-home-npm
f
Hey @dhanvi, subsequent
npm install
is much faster with cached
node_modules
.
To add a bit of context, caching
~/.npm
mostly saves the downloading time. But you’d still need to build out the node_modules tree, which is the time consuming part.
d
Got it fair enough, since the build environment is consistent it should be fine most of the time, curious if it will impact when the underlying OS on the build system is upgraded/changed.
f
Currently, different generations of the General Purpose build images are all Ubuntu based, and we haven’t heard ppl ran up against it yet.
You can always do a force deploy to throw away the cache https://seed.run/docs/manually-deploying.html#force-deploys