ipld-raw - npm Package Versions

7.0.1 (2021-08-11)

<a name="6.0.0"></a>

7.0.1 (2021-08-11)

<a name="6.0.0"></a>

6.0.0 (2020-08-04)

Bug Fixes

• replace node buffers with uint8arrays (#49) (0bb211a)

BREAKING CHANGES

• • util.serialize now returns a Uint8Array

<a name="5.0.0"></a>

5.0.0 (2020-05-06)

Bug Fixes

• package: update cids to version 0.8.0 (94e1db9)
• issue #16 - Throw error on resolving non-root path (#43) (a5b53be)

BREAKING CHANGES

• non-root paths throw an error

Prior to this change a call to the resolver with a path like this:

resolver.resolve(blob, '/a/b/c/d')

would just return the blob and an empty remainder path.

With this commit, it will throw an Error as there is no such path.

<a name="4.0.1"></a>

4.0.1 (2020-01-13)

Bug Fixes

• package: update multicodec to version 1.0.0 (fdbeed6)
• package: update multihashing-async to version 0.8.0 (60c06c1)

<a name="4.0.0"></a>

4.0.0 (2019-05-10)

Bug Fixes

• package: update cids to version 0.7.0 (0feb2fa)

BREAKING CHANGES

• package: Returned v1 CIDs now default to base32 encoding

Previous versions returned a base58 encoded string when toString()/ toBaseEncodedString() was called on a CIDv1. It now returns a base32 encoded string.

<a name="3.0.0"></a>

3.0.0 (2019-05-08)

Bug Fixes

• install step (25daf7a)
• package: update cids to version 0.6.0 (5f70e4e)
• package: update multihashing-async to version 0.6.0 (b2bb041)

Features

• new IPLD Format API (88dfb29)

BREAKING CHANGES

• The API is now async/await based

There are numerous changes, the most significant one is that the API is no longer callback based, but it using async/await.

For the full new API please see the [IPLD Formats spec].

<a name="2.0.1"></a>

2.0.1 (2018-06-29)

Bug Fixes

• resolver.tree allow options to be ommitted (2903bf7), closes #4

Features

• add defaultHashAlg (b7db79b)
• add util.cid options (#13) (bb2fbf7), closes ipld/interface-ipld-format#40

<a name="2.0.0"></a>

2.0.0 (2018-02-12)

Bug Fixes

• use binary blobs directly (6fc00cd)

BREAKING CHANGES

• Everyone calling the functions of resolve need to pass in the binary data instead of an IPFS block.

So if your input is an IPFS block, the code changes from

resolver.resolve(block, path, (err, result) => {…}

to

resolver.resolve(block.data, path, (err, result) => {…}

<a name="1.0.7"></a>

1.0.7 (2017-11-07)

<a name="1.0.5"></a>