I use a custom cache due to single-repo layout, with client and server in different folders. It did not seem the node cache worked for me this way.
I needed to do a cache to run npm install in one step, and npm test in another step, otherwise the node_modules did not seem to exist.
However, if i update the modules, say, add a dependency or update version of one, the cache does not seem to be updated by this in my npm install step?
Is this intended, or can i make my cache be updated if it detects a difference? Or is it simply better to use install and test in the same step, and then cache that? I guess i would get the latest version that way, but cache it for faster install times.
In regards to the last part of your question, the caches only update approximately every 7 days. There is a feature request to get them to update when there is a difference detected here: https://bitbucket.org/site/master/issues/16314/smarter-cache-invalidation it's not a priority at the moment, but if you vote for it and watch it you can see if that status changes.
Sorry that I don't have better news!
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events