Migrating to [email protected] and [email protected]
A migration guide for refactoring your application code from
[email protected]to[email protected]
The upgrade to [email protected] incorporates an update to [email protected] but no API changes.
If your application uses only the default libp2p config there is nothing to do.
If you supply a custom libp2p instance to the ipfs factory function you should consult the [email protected] upgrade guide for any changes you need to make.
[email protected] now uses [email protected], this means instances of the CID class now come from that module and not [email protected] so any instanceof checks your codebase has may break if instances are compare to the class loaded from a different module version.
If your project also has a dependency on the multiformats module, it should be updated to 10.x.x in line with js-ipfs.