Rhys Arkins ac09b9d7cd feat: cache npm results in memory per-run ... We currently use got’s inbuilt caching for npmjs, however it still results in a roundtrip/304 even when cached. The when using presets is that a package like renovate-config-default gets looked up 10+ times unnecessarily. With this feature we assume that npm lookups don’t change for the duration of a run, and even if they did then we’d prefer the reliability of using the first lookup. Closes #1389		2018-01-15 11:53:02 +01:00
..
config	fix: propagate registry-failure errors to avoid config validation warnings	2018-01-14 18:58:49 +01:00
logger	fix: writeToken -> forkToken (#1295)	2017-12-14 11:47:00 +01:00
manager	feat: cache npm results in memory per-run	2018-01-15 11:53:02 +01:00
platform	feat: prHourlyLimit	2018-01-11 11:56:16 +01:00
workers	feat: cache npm results in memory per-run	2018-01-15 11:53:02 +01:00
.eslintrc.js	refactor: use global logger (#1116)	2017-11-08 06:44:03 +01:00
renovate.js	Refactor config definitions and onboarding values (#360)	2017-06-26 13:08:57 +02:00