Franck R.

@achingbrain, any chance we could get the release please? This contains few bug fixes I'd love to get :) https://github.com/ChainSafe/js-libp2p-gossipsub/issues/305 and https://github.com/libp2p/js-libp2p-mplex/issues/191

> @D4nte soon! I'm just treading carefully around some of the protocol stream limiting stuff as it will cause things to break if the limits are not set correctly. >...

The issue I was referring to: https://github.com/ChainSafe/js-libp2p-gossipsub/issues/306

> I found that the [`Libp2pModules`](https://github.com/libp2p/js-libp2p/blob/58d4f9a91542f180907689319d159b326f71096d/src/index.js#L66) type for the config is missing keys for `peerDiscovery` and `dht`. It is also missing the key for `pubsub`.

I guess the issue is that other maintainer tell you to add the `require` property in their docs when it is not needed :)

I am guessing this is why it is not possible to use yarn 2 with ts-proto? I am getting the following error: ``` /home/froyer/src/status-im/js-waku/.pnp.js:17184 throw firstError; ^ Error: ts-proto-descriptors tried...

> ...fwiw I think personally in downstream projects, I would mark ts-proto as a devDependency (it's a code generator that is only used at build time) and then add explicit...

@oskarth considering our discussion from yesterday regarding wrapping nim-waku functionalities in WakuJS instead of rewriting them in JS. We agreed that for standard functionalities, a re-write in JS is the...

Same issue here: https://github.com/status-im/js-waku/runs/2593777765 despite the incident marked as resolved.

Maybe look into the shiplift crate so you don't create a docker api client from scratch.