The contents of this repo have been merged into ipfs/js-ipfs.
Please open issues or submit PRs there.
A test suite and interface you can use to implement an IPFS core interface.
The primary goal of this module is to define and ensure that both IPFS core implementations and their respective HTTP client libraries offer the same interface, so that developers can quickly change between a local and a remote node without having to change their applications. In addition to the definition of the expected interface, this module offers a suite of tests that can be run in order to check if the interface is used as described.
The API is presented with both Node.js and Go primitives. However, there are no actual limitations keeping it from being extended for any other language, pushing forward cross compatibility and interoperability through different stacks.
- JavaScript IPFS implementation
- JavaScript IPFS HTTP Client Library
- JavaScript IPFS postMessage proxy
Send in a PR if you find or write one!
Include this badge in your readme if you make a new module that implements interface-ipfs-core API.
[](https://github.com/ipfs/interface-ipfs-core)In JavaScript land:
npm install interface-ipfs-coreIf you want to run these tests against a go-ipfs daemon, checkout ipfs-http-client and run test tests:
git clone https://github.com/ipfs/js-ipfs-http-client
npm install
npm test
Install interface-ipfs-core as one of the dependencies of your project and as a test file. Then, using mocha (for Node.js) or a test runner with compatible API, do:
const tests = require('interface-ipfs-core')
const nodes = []
// Create common setup and teardown
const createCommon = () => ({
// Do some setup common to all tests
setup: async () => {
// Use ipfsd-ctl or other to spawn an IPFS node for testing
const node = await spawnNode()
nodes.push(node)
return node.api
},
// Dispose of nodes created by the IPFS factory and any other teardown
teardown: () => {
return Promise.all(nodes.map(n => n.stop()))
}
})
tests.block(createCommon)
tests.config(createCommon)
tests.dag(createCommon)
// ...etc. (see src/index.js)tests.repo.version(createCommon)tests.repo.gc(createCommon, { skip: true }) // pass an options object to skip these tests
// OR, at the subsystem level
// skips ALL the repo.gc tests
tests.repo(createCommon, { skip: ['gc'] })
// skips ALL the object.patch.addLink tests
tests.object(createCommon, { skip: ['patch.addLink'] })tests.repo.gc(createCommon, { skip: ['should do a thing'] }) // named test(s) to skip
// OR, at the subsystem level
tests.repo(createCommon, { skip: ['should do a thing'] })tests.repo.gc(createCommon, { only: true }) // pass an options object to run only these tests
// OR, at the subsystem level
// runs only ALL the repo.gc tests
tests.repo(createCommon, { only: ['gc'] })
// runs only ALL the object.patch.addLink tests
tests.object(createCommon, { only: ['patch.addLink'] })tests.repo.gc(createCommon, { only: ['should do a thing'] }) // only run these named test(s)
// OR, at the subsystem level
tests.repo(createCommon, { only: ['should do a thing'] })In order to be considered "valid", an IPFS core implementation must expose the API described in /SPEC. You can also use this loose spec as documentation for consuming the core APIs. Here is an outline of the contents of that directory:
- Files
- Graph
- Name
- Network
- Node Management
Feel free to join in. All welcome. Open an issue!
This repository falls under the IPFS Code of Conduct.
Copyright (c) Protocol Labs, Inc. under the MIT License. See LICENSE.md for details.