Update pre-async/await js-ipfs usage across PL repos

[andrew]

There are still a number of repos across ipfs/ipld/libp2p that are using js-ipfs < 0.41 that can be confusing to people looking for examples:

repo	version	manifest file	issue/pr
ipfs-shipyard/ipfs-companion	0.40.0	package.json	ipfs/ipfs-companion#811
ipld/js-ipld-graph-builder	^0.32.3	package.json	ipld/js-ipld-graph-builder#40
ipfs-shipyard/ipfs-share-files	^0.33.1	package.json	ipfs-shipyard/ipfs-share-files#75
ipfs/benchmarks	^0.34.0	tests/package.json	ipfs/benchmarks#276
ipfs-shipyard/ipld-explorer	^0.34.4	package.json	ipld/explore.ipld.io#65
ipfs-shipyard/js-idm-wallet	git://github.com/satazor/js-ipfs.git#ipfs-camp	package.json
ipfs-shipyard/js-idm-client	git://github.com/satazor/js-ipfs.git#ipfs-camp	package.json
libp2p/js-libp2p	~0.34.4	examples/delegated-routing/package.json	libp2p/js-libp2p#507
ipfs-shipyard/ipfs-npm-registry-mirror	~0.36.3	packages/common/package.json	ipfs-shipyard/ipfs-npm-registry-mirror#17

[oed]

ipfs-shipyard/ipfs-pubsub-1on1#11

[achingbrain]

@andrew could you open issues on the affected repos? Their owners may not check this issue so likely won't know that they should update.

If they aren't maintaining them any more, they should probably be archived or at least a big note should be put in the readme.

Also, some repos have been updated, can you update this table occasionally?

[andrew]

I've updated the table, removed rows that have been upgraded and added links to PRs that will update js-ipfs

[lidel]

Based on triage discussion, closing as stale: assuming if a project did not update by now, either there is an unrelated blocker, or project is not important enough/maintained.