Alex Potsides

> could we split the identify module into two? This sounds like a good solution since it's a separate protocol, it could be exported from `@libp2p/identify` for convenience though since...

The latest patch release of js-libp2p & supporting modules have shipped with some fixes for running under react-native. There's a new demo app at https://github.com/ipfs-shipyard/js-libp2p-react-native which uses Expo to build...

☝️ cc: @shamilovtim

Thanks for taking a look. > "exports" is a blunt hammer that caused more harm than good when I tried to use it I'm interested in what's still broken here,...

Thanks for opening this - would you like to open a PR that adds the missing documentation?

Related: https://github.com/libp2p/js-libp2p/issues/1573

A runtime check seems reasonable but this really shouldn't be allowed by the types.

Still a draft as there's more work to do, tests aren't passing yet, etc - one obvious thing is this PR adds yamux to the monorepo which accounts for most...

@wemeetagain I put a simple benchmark together here - https://gist.github.com/achingbrain/7e65ca748326d3b87b81508020a3321d Results are on there but TLDR is node streams are fastest, web streams are a bit slower and node streams...

On the basis of the benchmarks showing a performance degradation with the switch to web streams, is this something we actually want to do? My gut feeling would be no,...