minimum cache timeout option #2249

Closed
kamholz opened this Issue Mar 9, 2012 · 0 comments

2 participants

@kamholz

It would be nice if npm had an explicit setting for the minimum cache age, so that if a module's already fetched info's age is less than the minimum, it will be used rather than hitting the registry again. This would significantly reduce the number of registry hits for common dependencies -- if I do npm update -g, for example, I get many hits for things like mkdirp, lru-cache, traverse, abbrev, etc. I should be able to tell npm that it's ok to go with info that is 60 seconds stale, or whatever.

@isaacs isaacs closed this in 828718b Mar 14, 2012
@isaacs isaacs added a commit to isaacs/node that referenced this issue Mar 15, 2012
@isaacs isaacs 2012.03.15 Version 0.6.13 (stable)
* Windows: Many libuv test fixes (Bert Belder)

* Windows: avoid uv_guess_handle crash in when fd < 0 (Bert Belder)

* Map EBUSY and ENOTEMPTY errors (Bert Belder)

* Windows: include syscall in fs errors (Bert Belder)

* Fix fs.watch ENOSYS on Linux kernel version mismatch (Ben Noordhuis)

* Update npm to 1.1.9
  - upgrade node-gyp to 0.3.5 (Nathan Rajlich)
  - Fix npm/npm#2249 Add cache-max and cache-min configs
  - Properly redirect across https/http registry requests
  - log config usage if undefined key in set function (Kris Windham)
  - Add support for os/cpu fields in package.json (Adam Blackburn)
  - Automatically node-gyp packages containing a binding.gyp
  - Fix failures unpacking in UNC shares
  - Never create un-listable directories
  - Handle cases where an optionalDependency fails to build
9f7f86b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment