js-waku
js-waku copied to clipboard
Release 0.25.0
Track the blockers for the next release.
A lot of refactoring has happen since the last release:
- Migration to ESM only
- Upgrade to latest libp2p* libraries
- New API for a more modular architecture
Release candidates under the next
flag will be published to help prepare this release.
Tasks
Remaining tasks to do before release
- [ ] Use release candidate in all examples https://github.com/waku-org/js-waku-examples/issues/56
- [ ] Investigate issues with Waku Relay being unreliable (related to
protons
performance issue? https://github.com/ipfs/protons/issues/51) - [ ] Use a proto encoding/decoding that handles default as expected (ref: https://github.com/ipfs/protons/pull/48)
- [ ] Use
[email protected]
once published. Not a strong blocker but a recommended one. - [x] https://github.com/status-im/js-waku/issues/895
- [ ] Ensure full test suite pass https://github.com/status-im/js-waku/issues/902
feedback from @filoozom
On latest master, it seems a bit difficult to import createWaku.
import { createWaku, CreateOptions } from 'js-waku/dist/lib/create_waku'
works for types, but one needs to useimport { createWaku, CreateOptions } from 'js-waku/lib/create_waku'
for the imports to actually work. Also, it's not quite clear how to connect to static peers., as I can't importPeerDiscoveryStaticPeers
(maybe related to the same issue as forcreateWaku
)
https://github.com/status-im/js-waku/pull/893 helps with the proto behaviour
export issue https://github.com/status-im/js-waku/pull/894
Done!