feat: close connections when too many streams are opened

[achingbrain]

If we hit the inbound stream limit and the remote peer continues to attempt to open new streams at a rate we consider to be unreasonable, close the connection.

Mplex has no notion of backpressure so this is all we can really do to protect ourselves.

[github-actions]

🎉 This PR is included in version 5.2.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[fryorcraken]

rate-limiter-flexible uses a NodeJS API util, which means to use mplex in the web, we now need to handle the polyfilling of util.

It looks like it does not need to be polyfilled:

https://github.com/animir/node-rate-limiter-flexible/blob/d070b20cadca8b17246653d851256ee5f859f35b/lib/RateLimiterRes.js#L55

However, it is still makes the library less accessible as one still need to specify that util polyfill is not needed. For example. when using a React app then needs to eject or use craco to override the webpack config.

What are your thoughts on this? Can we aim to avoid using Node APIs in libp2p libs and their dependencies? Should this only be an library consumer concern?

Cheers.

[fryorcraken]

It looks like it does not need to be polyfilled:

I was incorrect, it does need to be polyfilled as util.inspect.custom is called.

Uncaught TypeError: util.inspect is undefined
    35398 RateLimiterRes.js:55

[fryorcraken]

Actually got resolved overnight: animir/node-rate-limiter-flexible#179

[wemeetagain]

Yeah, ideally we don't rely on nodejs apis in our libraries. This one slipped by me