js-waku/packages
fryorcraken.eth 89571ff497
feat!: remove peer exchange from protocols to wait on by default
This is because peer exchange is still experimental and not enabled
on all prod fleets.

The issue is that we could be connected to a remote peer with relay/
filter/lightpush yet never resolve because peer exchange is missing.

This also shows the limit of this function logic which should be
addressed as we dive deeper in peer management.
2022-12-20 23:00:30 +11:00
..
byte-utils build(deps-dev): bump cspell from 5.21.2 to 6.17.0 2022-12-13 13:46:02 +11:00
core feat!: remove peer exchange from protocols to wait on by default 2022-12-20 23:00:30 +11:00
create chore: release @waku/create@0.0.6 2022-12-19 16:58:30 +11:00
dns-discovery chore: release @waku/dns-discovery@0.0.3 2022-12-15 14:48:55 +11:00
enr chore: release @waku/enr@0.0.3 2022-12-15 14:41:30 +11:00
interfaces chore: release @waku/interfaces@0.0.6 2022-12-15 14:43:15 +11:00
libp2p-utils chore: release @waku/libp2p-utils@0.0.1 2022-12-15 14:37:56 +11:00
message-encryption fix: export `Encoder` and `Decoder` types 2022-12-20 16:11:41 +11:00
peer-exchange build(deps-dev): bump cspell from 5.21.2 to 6.17.0 2022-12-13 13:46:02 +11:00
proto build(deps-dev): bump cspell from 5.21.2 to 6.17.0 2022-12-13 13:46:02 +11:00
tests test: remove `--nat` option when starting nwaku 2022-12-15 13:54:07 +11:00