You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for sharing your work. It has proven to be very useful for speeding up my CI pipeline.
Some background - My development CI process currently works like this:
1. npm-cache install npm # Install (hopefully from cache)
2. npm update # Update any new dependencies from last cache
3. npm-cache install --forceRefresh npm # Re-archive the dependencies
In my package.json some of my internal project dependency versions are set to "latest" (it's continuous delivery-related decision...). Since the cache is keyed to a hash of the package.json file itself and not the latest versions of each dependencies, I need to run an update after the initial install to pick up any changes from the first cache.
It would be great if I could do this all in one shot. Something like an: npm-cache update npm, where upon a cache-hit, it extracts, runs update, then re-archives (otherwise on cache-miss, just install as normal).
Or instead/additionally, a new command like npm-cache rearchive npm would be helpful in speeding up my step 3 (I don't need to actually run an install again, only need to cache it).
I might be missing an undocumented feature, but wanted to ask about this regardless. Thanks again!
The text was updated successfully, but these errors were encountered:
Thanks for sharing your work. It has proven to be very useful for speeding up my CI pipeline.
Some background - My development CI process currently works like this:
In my package.json some of my internal project dependency versions are set to "latest" (it's continuous delivery-related decision...). Since the cache is keyed to a hash of the package.json file itself and not the latest versions of each dependencies, I need to run an update after the initial install to pick up any changes from the first cache.
It would be great if I could do this all in one shot. Something like an:
npm-cache update npm
, where upon a cache-hit, it extracts, runs update, then re-archives (otherwise on cache-miss, just install as normal).Or instead/additionally, a new command like
npm-cache rearchive npm
would be helpful in speeding up my step 3 (I don't need to actually run an install again, only need to cache it).I might be missing an undocumented feature, but wanted to ask about this regardless. Thanks again!
The text was updated successfully, but these errors were encountered: