Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Support more IPLD types #2853

Closed
achingbrain opened this issue Sep 18, 2019 · 3 comments
Closed

Support more IPLD types #2853

achingbrain opened this issue Sep 18, 2019 · 3 comments
Labels
exp/novice Someone with a little familiarity can pick up kind/feature pkg:http-client Issues related only to ipfs-http-client

Comments

@achingbrain
Copy link
Member

js-IPFS has separate IPLD config for node and the browser that omits some of the more obscure heavyweight types to save on bundle size.

From what I can see this module only supports dag-pb, dag-cbor and raw types.

It should probably follow a similar strategy to include more types.

It'll also help us fix up the "Explore the Etherum Blockchain" example - #1453

@mikeal
Copy link
Contributor

mikeal commented Sep 18, 2019

FYI, the next major version of the new Block API will probably chop this down even more, potentially shipping with nothing except for raw and asking the user to configure each codec you want to support.

We’re trying to get our default bundle sizes much lower and shipping codecs you don’t use are a big source of bundle bloat from IPLD.

@alanshaw
Copy link
Member

alanshaw commented Nov 5, 2019

We could expose a loadFormat option or might be worth including IPLD like in ipfs-inactive/js-ipfs-http-client#755?

@achingbrain achingbrain transferred this issue from ipfs-inactive/js-ipfs-http-client Mar 9, 2020
@achingbrain achingbrain added exp/novice Someone with a little familiarity can pick up kind/feature pkg:http-client Issues related only to ipfs-http-client labels Mar 9, 2020
@achingbrain
Copy link
Member Author

Fixed in #3073

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
exp/novice Someone with a little familiarity can pick up kind/feature pkg:http-client Issues related only to ipfs-http-client
Projects
None yet
Development

No branches or pull requests

3 participants