Open necccc opened 7 years ago
Hi,
we're using our npme instance as a read through cache, and and the following problem came up today:
postcss
undefined
npm info postcss@6.0.1 npm http request GET https://our.npme.instance/postcss npm http 304 https://our.npme.instance/postcss undefined
npm info postcss
npme remove-package postcss
Is it possible to set the cache TTL? Or should npme get notified if a cached module is updated at the upstream?
Our config uses https://replicate.npmjs.com as upstream url, the policy is white-list
https://replicate.npmjs.com
white-list
Side note: this is really inconvenient, as this was one of the main reasons we've switched over npme from sinopia :(
Hi,
we're using our npme instance as a read through cache, and and the following problem came up today:
postcss
module, which 6.0.1 at the momentundefined
(which is also weird as it is)npm info postcss
it said the latest is 5.2.16npme remove-package postcss
to purge the cached copyIs it possible to set the cache TTL? Or should npme get notified if a cached module is updated at the upstream?
Our config uses
https://replicate.npmjs.com
as upstream url, the policy iswhite-list
Side note: this is really inconvenient, as this was one of the main reasons we've switched over npme from sinopia :(