chore: update deps

[alanshaw]

Needed for next js-ipfs release. Had to port some changes from #7

Depends on:

• fix: response for findpeer and findprovs ipfs-inactive/js-ipfs-http-client#1039

cc @achingbrain

[alanshaw]

@jacobheun I could use some help here.

The tests are now failing because findProvs in ipfs-http-client now only returns values for messages where the Type is 4 (Provider).

Previously it was returning values for all messages with a Responses array because ipfs-api did not do any filtering on the Type.

What is the right thing to do here? Do we need a streaming findProvs so you can get hold of this extra info?

[jacobheun]

@alanshaw fyi, i pushed up a lint fix.

Taking a look at the tests

[jacobheun]

What is the right thing to do here? Do we need a streaming findProvs so you can get hold of this extra info?

We only care about actual providers, I don't think we need to care about the extra information. It looks like the tests will need to be updated

[achingbrain]

I'll update #7 once the dust settles on this.

[jacobheun]

The provide/findProv calls are really inconsistent, looking into it more.

[jacobheun]

@alanshaw this should be fixed with ipfs-inactive/js-ipfs-http-client#1041. The test failures on CI are due to ipfsd-ctl resolving the current version of the http client instead of the fixed branch. Patching that locally makes the tests here pass every time.

[alanshaw]

@jacobheun it still fails 🙀

[jacobheun]

@alanshaw clearing the node_modules cache on CI and rerunning to see if it's just an issue with the transitive deps cacheing.

[jacobheun]

All better, it was ipfsd-ctl also using ipfs-http-client that was causing the issue. Blasting the cache allowed the fix to be all fix-y like.