Support and reuse ipfs.types and ipfs.util

[lidel]

Background

I requested something similar some time ago (), and it just landed 🚀
Since last week a set of data types and utils is being exposed directly from the IPFS instance under ipfs.types and ipfs.util:

• ipfs.types.Buffer
• ipfs.types.PeerId
• ipfs.types.PeerInfo
• ipfs.types.multiaddr
• ipfs.types.multibase
• ipfs.types.multihash
• ipfs.types.CID
• ipfs.types.dagPB
• ipfs.types.dagCBOR
• ipfs.util.crypto
• ipfs.util.isIPFS

Source: ipfs-inactive/interface-js-ipfs-core#252, SPEC/TYPES.md, SPEC/UTIL.md

Availability Status

• js-ipfs-api (v20.0.0): , feat: Provide access to bundled libraries when in browser ipfs-inactive/js-ipfs-http-client#732
• js-ipfs (waiting for release): feat: Provide access to bundled libraries when in browser js-ipfs#1297

Tasks

• switch to js-ipfs-api and js-ipfs with support for these endpoints
• switch to bundled types and utils
• remove duplicate dependencies
• expose ipfs.types and ipfs.util under windows.ipfs (if feasible)

[lidel]

Closing due to #589 (comment)