We started using the pipelines cache with our node builds recently.
It definitely accelerates the builds, but we have found a problem when we update a module's version that is a dependency for the actual build that is caching the node_modules.
Basically, if you have a dependency that gets updated to a newer version (for example an internal module hosted in a private node registry). The cache does not update.
Upon build and install it works because the local node_modules gets updated, but the cached version doesn't get updated... so the next step if you don't run "npm install" as well, it will download the un-updated version of the cache and cause issues (say for example on a deployment step). Ideally we wouldn't have to do npm install on every step...
So this issue is about seeing if its possible to make the cache update every time a a change in the node_modules directly is detected.