fix: replace node buffers with uint8arrays

[achingbrain]

Depends on:

• fix: replace node buffers with uint8arrays multiformats/js-cid#117

BREAKING CHANGE:

• util.serialize now returns a Uint8Array
• util.cid returns CIDs with a breaking API change - see fix: replace node buffers with uint8arrays multiformats/js-cid#117 for changes

[codecov]

Codecov Report

Merging #134 into master will not change coverage.
The diff coverage is 83.33%.

@@           Coverage Diff           @@
##           master     #134   +/-   ##
=======================================
  Coverage   96.26%   96.26%           
=======================================
  Files           3        3           
  Lines         107      107           
=======================================
  Hits          103      103           
  Misses          4        4           

Impacted Files	Coverage Δ
src/util.js	96.25% <80.00%> (+0.04%)	⬆️
src/resolver.js	95.65% <100.00%> (-0.19%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4646b62...41cb24e. Read the comment docs.

[rvagg]

Fine, with concern about TOC format change, and pending resolution of the CID change.

Do we know that the pass to and from borc is happy with Uint8Arrays too so this is a complete conversion?

[rvagg]

can we avoid this as the top-level container of the TOC?

[achingbrain]

Done!

[vmx]

In your original comment you mention:

• util.cid returns v1 CIDs

as breaking change. But isn't that the case already?

[achingbrain]

Maybe it's badly worded. I meant that the return type of the method has changed - it's now js-cid@v1.0.0, with the renamed .bytes property, not v0/v1 CID/multihashes.