Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Re-Archive feature request #12

Open
cgmartin opened this issue Aug 23, 2015 · 0 comments
Open

Re-Archive feature request #12

cgmartin opened this issue Aug 23, 2015 · 0 comments

Comments

@cgmartin
Copy link

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants