Gar

Yes matching what is likely to land in node itself would be the best option if you went down that path. There's no current implementation of this functionality in npm...

I believe this was fixed in `v7.7.0`, the prompt code wasn't being called properly but it should be now.

Can you test this in `[email protected]`? `npm exec` had a lot of bugfixes in that release, including properly installing git repos.

This looks like it was fixed. ```sh ~/D/n/s/empty $ npx wraithgar/gar-create-test Need to install the following packages: github:wraithgar/gar-create-test Ok to proceed? (y) Gar's test create script version 2.0.3 ```

What exactly are you typing? You removed the "steps to reproduce" so we don't have any actual reproducible steps.

does `npm install @protocols/node-focas` work? ETA: Is npm configured to authenticate to that tarball url? It looks like gitlab has docs for this https://docs.gitlab.com/ee/user/packages/npm_registry/ The 404 seems to indicate this...

That would attempt to install `https://github.com/protocols/node-focas` from git (which currently doesn't exist) and not the scoped package.

Changes to the npm registry itself would have to go through [support](https://www.npmjs.com/support). The npm cli interacts with that and many other registries (i.e. github packages registry, private registries, azure artifacts)....

So ... this issue made me do a little digging into `pacote` / `npm-registry-fetch` / `make-fetch-happen` and it turns out that the npm cli is not leveraging http agents, even...

I was mistaken! `agent` is obeyed by `make-fetch-happen`!!! `https://github.com/npm/make-fetch-happen/blob/main/lib/agent.js#L44-L46` You should be able to generate your own keepalive agent and pass that in as `agent` to pacote opts.