js-waku icon indicating copy to clipboard operation
js-waku copied to clipboard

JavaScript implementation of Waku v2

Results 206 js-waku issues
Sort by recently updated
recently updated
newest added

## Problem When attempting to send many messages back to back we run into an error: `ERR_TOO_MANY_OUTBOUND_PROTOCOL_STREAMS` ## Steps to reproduce ```js import { createLightNode, waitForRemotePeer, createEncoder, utf8ToBytes, } from...

enhancement

This is a **feature request** ## Problem For protocol implementations (eg Filter), we have access to certain `statusCode` that the remote peer might respond with. Based on specific `statusCode`, returning...

enhancement

## Problem The Filter implementation currently `throws` `Error` to handle non-success scenarios. This needs a change to using error codes instead: #1694 ## Solution Move all `throw`s to returning error...

This is a **support request** ## Problem With our work on splitting protocol implementations to `Core` and `SDK`, we also introduced two types for each implementation class: `Core` and `SDK`...

enhancement

## Problem Tests that run against cluster id 1 (The Waku Network) require running an nwaku node with a sepolia RPC url. When adding this parameter, the nwaku node will...

## Problem https://github.com/waku-org/js-waku/issues/1965 ## Solution This PR: - adds connection timeout, retry backoff base and maximum retries for stream creation - sets up a `Promise.race()` between successful stream creation and...

## Problem `IReceiver` currently expects `subscribe()` to be a function on the class implementation that we previously used for Filter. We moved to `createSubscription()` method instead, which is more generic....

enhancement
good first issue

This is a **change request** ## Problem When a js-waku app is ran on HTTP (not HTTPS) and also not `localhost` connection-manager will silently fail to connect to any node....

This is a **bug report/feature request/support request/change request** ## Problem The subscribe function for filter accepts either a single decoder or an array of decoders. This leads to a lot...

enhancement

This is a **bug report** ## Problem nwakujs-waku interop saw flakiness when we dial two nwaku nodes, from js-waku, one after the other -- the connections seems to be dropping....

bug
test