Skip to content

Drop embedded js-ipfs (ipfs-core); keep HTTP Kubo API - #1

Open
IshmaelRogers wants to merge 2 commits into
mainfrom
feat/drop-embedded-js-ipfs
Open

IshmaelRogers wants to merge 2 commits into
mainfrom
feat/drop-embedded-js-ipfs

Conversation

@IshmaelRogers

Copy link
Copy Markdown

Removes the EOL embedded js-ipfs (ipfs-core) path, keeping the HTTP-to-Kubo mode the library already had. CIDs stay byte-identical (same add options + cid/hash math). Endpoint via FORGE_IPFS_API/IPFS_API; engines.node >=20. This modernizes the shared IPFS wrapper the whole DigiAssetX family (digiasset-encoder/decoder/lookup/input) depends on, so a single overrides entry removes js-ipfs from the entire tree.

The upstream already had an HTTP mode against the Kubo RPC API (api/v0) via got;
only the embedded-node path used ipfs-core (EOL). Remove that path and _coreMode,
keeping the HTTP behavior and therefore byte-identical CIDs (same add options,
same cid<->hash math). Endpoint from FORGE_IPFS_API / IPFS_API. Drop ipfs-core
and the now-unused sleep-promise; pin engines node>=20.
Modern Kubo returns 500 ("removed, use 'ipfs dag' or 'ipfs files'") for
object/stat. files/stat on /ipfs/<cid> returns the same CumulativeSize.
Verified against a live kubo daemon: full API smoke (add/cat/pin/size +
cid<->hash inverse + deterministic CID) passes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants