In3 API for TS doesn't run with any example.

[VanessaPC]

Steps to reproduce

I am trying to create a web app using the instructions from here: https://in3.readthedocs.io/en/latest/api-ts.html and following the examples from here: https://github.com/slockit/in3/blob/master/examples/src/in3DirectAPI.ts and I can't get anything to log out.

my versions of in3 and web3 are:

   "web3": "^1.2.9"
    "in3": "^2.1.3",

And I'm using a normal NodeJS server with Express. This is all I get:

UnhandledPromiseRejectionWarning: Error: tried eth_getBlockByNumber("0x0",false) to https://in3-v2.slock.it/mainnet/nd-2 but failed and can not recover (No nodes found that fullfill the filter criteria ) from wrong response  : Error: No nodes found that fullfill the filter criteria

And this is after a day of trying to request different hashes by blocks, numbers, etc.. The previous error is by copying the code from : https://github.com/slockit/in3/blob/master/examples/src/in3DirectAPI.ts

Expected behavior

Anything should login when I try to get information with the hash given in the test.

Actual behavior

I get errors.

System configuration

MacOS 10.15.1

Incubed version

"in3": "^2.1.3",

Request

Incubed Configuration

Chain

[VanessaPC]

This Error is in the wrong repo. It should be under the in3 JS, sorry about it, I was looking at the code in general to find the errors.

[cerealkill]

Hi Vanessa, first of all, thank you very much for trying it out and writing this issue, we really appreciate the feedback.

We are currently moving away from TS to maintain support for WASM only, which should work pretty much the same.

To migrate just change your package name to in3-wasm and version to 3.0.3.

Also, because in3 is a network run by the community, it can sometimes be unavailable. The response you have got there points out to this case, but it is still worth updating your client and double-checking.

Let us know if the issue persists, thanks again!

• Paul