A JavaScript HTTP client library for interacting with IPFS daemons via their HTTP API.
js-ipfs-http-client is a JavaScript library that provides a client for the IPFS HTTP API, allowing applications to interact with IPFS daemons. It enables developers to perform IPFS operations like adding files, retrieving content, and managing the network programmatically. The library solves the problem of integrating IPFS functionality into JavaScript applications without running a full node directly.
JavaScript developers building decentralized applications, tools, or services that need to interact with IPFS nodes via HTTP. It's suitable for both frontend and backend developers working with IPFS.
Developers choose js-ipfs-http-client because it offers a standardized, spec-compliant interface to IPFS, supports both browser and Node.js environments, and provides utility functions that simplify common tasks like adding files from various sources.
[ARCHIVED] now part of the https://github.com/ipfs/js-ipfs repo
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Adheres to the interface-ipfs-core spec, enabling seamless switching between embedded and remote IPFS nodes, as highlighted in the README's API section.
Works in both browser and Node.js environments with configurable CORS and custom headers, supported via examples for Browserify, webpack, and CDN usage.
Includes globSource and urlSource for easy file addition from local filesystems or URLs, simplifying common IPFS operations as shown in the static utils section.
Supports global timeouts, custom HTTP headers, and additional options like AbortSignal, allowing fine-tuned control over HTTP requests per the README.
The library is no longer maintained independently; all development has moved to js-ipfs, meaning new issues or features require switching repositories, as stated at the top of the README.
Requires a running IPFS daemon with correct port configuration, adding setup complexity and potential latency compared to embedded solutions.
Browser usage necessitates manual CORS configuration on the IPFS server, which can be a barrier for web apps, as acknowledged in the CORS section with commands to whitelist domains.