I
I
JJ
V
J
JJJJJVJ
VV
D
I
I
I
J
npm~/.npm?J
node_modules right now. What goes into ~/.npm?JJJnpm install as a follow up to Pages running it for you, caching ~/.npm wouldn't have an effectJnode_modules is that it can break across node versions, OS versions, and won't work with npm ci since npm ci always nukes node_modules first. You want to cache the npm cache result, which is ~/.npm unless you're overriding the npm cache location.JJnpm ci altogether and (ought to) incorporate node version in the cache keyJnpm ci and not npm install to give reproducible builds?JJnode_modules folder. It's a path well trodden by other CI platforms and folks for years: https://stackoverflow.com/questions/42521884/should-i-have-travis-cache-node-modules-or-home-npm 
Jcd site && npm ci && ... as my build commandJ~/.npm was cached, I would benefit, but with node_modules cache I do notI
JIJJJcd site && npm ci && ...? If ~/.npm was cached, worst case I have to download a couple new dependencies even if my package-lock, etc. changesJpackage-lock.json would invalidate the cache key and mean the entire node_modules would be re-downloaded?J~/.npm just seems like a better solution to me and also means that any post-install scripts still run. Let's say I have an npm package that doesn't change version between installs, but has a postinstall that runs and pulls updated geoip data or something every time. That's not that uncommon of a use-case.Jnode_modules in its entirety and skipping the install step, that breaks that, vs caching ~/.npm and just running npm ci again which'll use that cache, run any normal hooks/scripts, and everything works as expected. You get the benefit of the cache, and any kinda of postinstall or other weird hooks/scripts run as expected.Jnpm install step entirely seems like a bad idea IJnode_modules here JJI It's currently saving me 8s, so I went from 83s to 75s...I
~/.npm~/.npm~/.npm~/.npm~/.npm~/.npm~/.npm~/.npmnode_modulesnode_modulesnode_modulesnode_modulesnode_modulesnode_modulesnode_modulesnode_modulesnpm installnpm installnpm installnpm cinpm cinpm cinpm cinpm cicd site && npm ci && ...cd site && npm ci && ...package-lockpackage-lock.jsonpostinstall22:30:34.197 Uploading to dependency cache
22:30:34.254 Skipping build output cache as it's not supported for your project