The error response content and error status code are also now returned up from the registry to the npm_lazy clients. for other errors are requests retried maxRetries times.
improved remote error handling (404's, 500's) for resources that are not in the cache (thanks 404's for are returned immediately (previously, npm_lazy returned a generic 500 error for 404's). introducing as a co-maintainer / core contributor, and a solid set of improvements to the error handling in npm_lazy. Better handling of npm private modules (#52, thanks in version 1.7.x. Added port, host, remote-url and external-url CLI command configurations (#47, thanks in version 1.8.x. Added support for private npm packages, thanks in version 1.10.x. The NPM registry now uses https for all connections, updated all internals and defaults to use https. This means that even when outages occur, you can install any package that has been installed at least once before. However, if contacting the registry fails, then the old version of the metadata is sent instead. If the JSON metadata is older than cacheAge (default: 1 hour), we will attempt to contact the registry first. Metadata files are never discarded until a newer version can be fetched successfully. Metadata files must parse as JSON if not, they are retried. 
Tarfiles are checked against the expected shasum, and cached forever if they match if not, they are retried.Invalid responses are rejected and retried:.If this fails, the request is retried (or failed). All HTTP requests are subject to a maximum fetch timeout (default: 5000 ms).Here are all the ways in which npm_lazy is resilient to registry failures: Metadata is expired periodically (default: 1 hour) so that the latest versions of packages are fetched.
No explicit need to manage packages or replication.
Lazy caching: When a package is requested the first time, it is cached locally. No database to install, replicate or manage. If 100 servers request the same package metadata at the same time, npm_lazy makes sure that (at most) only one request goes out to the npm registry. npm_lazy caches packages on your local network, making things faster and more predictable. npm can be slow, down or return random errors if you have large deploys.
0 kommentar(er)
