feat: export CID

[bluelovers]

avoid typescript esModuleInterop issues

[vmx]

@mikeal @rvagg could you have a look at this. You are deeper into JS stuff atm. Do you see a problem with such a self-reference?

[jacobheun]

This is likely related to multiformats/js-multiformats#18

[rvagg]

This is to avoid the default-exports problem, right @bluelovers? Over at ipld/team-mgmt#81 (comment) I was suggesting that as we go forward with ESM we might want to avoid default exports entirely where possible because of the dramas surrounding it. I imagine this is the same sort of problem but it only arises when using TypeScript (or other faux-ESM solutions?). I'm not clear on that part and how you'd trigger a problem with this package because it's not ESM but I think I'm starting to be a fan of exporting explicitly things for the next year or two!

[Gozala]

So many things have changed here that, I don't think thing is going to work anymore. I think the option moving forward is to address this, if it is an issue, in https://github.com/multiformats/js-multiformats

Hopefully soon enough we'll migrate to the new CIDs from there.