Danish Arora

ensure all async operations are "caught"/handled perhaps can find some rule in eslint around the same ideal to have a wide net sort of an approach

@weboko and @danisharora099 to look into possible solutions

while it shouldn't matter, but with js-libp2p example gossipsub is directly being used (no wait for ack), while lightpush uses req-res model (per stream) and requires to wait for ack....

some findings: - no peer discovered via js-waku has a component like `p2p/QmAlice/p2p/QmBob` as was seen in the browser findings (was checked right before sending to `libp2p.dial()` - was also...

update: js-libp2p supports circuit-relay: https://github.com/libp2p/js-libp2p/blob/a6be8f0f4bbd81826c2ca5d48ea6175b1fdf3ab9/doc/migrations/v0.42-v0.43.md?plain=1#L29

blocked with https://github.com/libp2p/js-libp2p/issues/2024

currently blocked until a sync with go-waku @richard-ramos (who is currently travelling) can be scheduled as there is an interop bug

the work enabling & testing circuit relay connections is being tracked in #1619 ---- 1. for go-waku, a few changes had to be made to allow for seamless testing, and...

Fully onboard with having an event-driven API, instead of/along with callbacks

- [ ] look into best practices for monorepo codebase structuring @danisharora099 @weboko