Deno destroys our npm private registry by making too many requests at the same time

[RoXuS]

Hi Team,

We have migrated one of our front on Deno + vite + lit, it works like a charm, thanks.

We use a private npm registry (verdaccio 5.x).

When we launch Deno run, all npm dependencies are fetched and our registry explode randomly (CPU 100% then it crashes).
We have tried to use a big instance (8 CPU) it better but not perfect (sometimes crash too)...
When we disable HTTP2 on our load balancer all is ok...

Not sure that is a Deno issue but it seems Deno request all dependencies too quickly and too hardly on our registry.

There is a way to slow down the speed at which Deno requests its dependencies?

The error:

Caused by:
    Error getting response at https://OUR-REGISTRY-URL/finalhandler for package "finalhandler": error sending request for url (https://OUR-REGISTRY-URL/finalhandler): http2 error: stream error received: refused stream before processing any application logic: http2 error: stream error received: refused stream before processing any application logic: stream error received: refused stream before processing any application logic

[RoXuS]

maybe link to seanmonstar/reqwest#976 ...

[magurotuna]

I believe this is the same issue as #21789. Once hyperium/h2#731 lands and we incorporate that change, this issue should be fixed.

[char8x]

It seems that all the PRs have been merged, shall we upgrade these dependencies?

[RoXuS]

That would be fantastic