pacote
pacote copied to clipboard
zkat
programmatic npm package and metadata downloader (moved!)
While the CLI probably doesn't need to worry about this much except in case of catastrophe, there's some user tooling that could really benefit from pacote's default mode refusing to...
So with the http client, it's possible for a request to die mid-stream. Right now, that just kinda implodes and starts the process over. Instead, we should emit `reset` events...
If a package manifest has no `bundleDependencies`, we should filter out any files contained within `node_modules` for it.
npm-registry-client shoots out all these special headers itself. A lot of them have to do more with specific npm features than just fetching packages. Move these headers out of pacote...
There's basically no coverage on them, but they might be a bit tricky to write due to having to set up and launch git daemons. Once the mocking utility's done,...
pacote is built for performance. Performance is meaningless without benchmarks and profiling. So. We need benchmarks. There should be benchmarks for each of the supported types (note: only registry ones...
Add various bits of noteworthy performance analytics to be collected on the fly, and log them out as things complete. Some ideas: * manifest fetch time * tarball fetch time...
Right now, there's a bunch of errors that get spit out by various deps and such that we use. The CLI eventually has to make its own decisions about these,...
`opt-check` was a pretty basic option handling mechanism but I'm not feeling great about it: it silently fails if it gets unexpected options (and those options are later requested), it...
pacote should have a step-by-step guide on how to use it. This is probably pretty straightforward, since the API surface is relatively small. Still, it's good to have this.