A client library for the IPFS HTTP API, implemented in JavaScript. This client library implements the interface-ipfs-core enabling applications to change between a embebed js-ipfs node and any remote IPFS node without having to change the code. In addition, this client library implements a set of utility functions.
This module uses node.js, and can be installed through npm:
$ npm install --save ipfs-apiNote: ipfs-api requires Node v4.x (LTS) or higher.
To interact with the API, you need to have a local daemon running. It needs to be open on the right port. 5001 is the default, and is used in the examples below, but it can be set to whatever you need.
# Show the ipfs config API port to check it is correct
$ ipfs config Addresses.API
/ip4/127.0.0.1/tcp/5001
# Set it if it does not match the above output
$ ipfs config Addresses.API /ip4/127.0.0.1/tcp/5001
# Restart the daemon after changing the config
# Run the daemon
$ ipfs daemonvar ipfsAPI = require('ipfs-api')
// connect to ipfs daemon API server
var ipfs = ipfsAPI('localhost', '5001', {protocol: 'http'}) // leaving out the arguments will default to these values
// or connect with multiaddr
var ipfs = ipfsAPI('/ip4/127.0.0.1/tcp/5001')
// or using options
var ipfs = ipfsAPI({host: 'localhost', port: '5001', procotol: 'http'})Same as in Node.js, you just have to browserify the code before serving it. See the browserify repo for how to do that.
You can use npmcdn to get the latest built version, like this
<script src="https://npmcdn.com/ipfs-api/dist/index.js"></script>This will export the IpfsApi constructor on the window object, such that:
var ipfs = window.IpfsApi('localhost', '5001')
If you omit the host and port, the api will parse window.host, and use this information. This also works, and can be useful if you want to write apps that can be run from multiple different gateways:
var ipfs = window.IpfsApi()
If are using this module in a browser with something like browserify, then you will get an error saying that the origin is not allowed. This would be a CORS ("Cross Origin Resource Sharing") failure. The ipfs server rejects requests from unknown domains by default. You can whitelist the domain that you are calling from by changing your ipfs config like this:
$ ipfs config --json API.HTTPHeaders.Access-Control-Allow-Origin "[\"http://example.com\"]"
js-ipfs-apifollows the spec defined byinterface-ipfs-core, which concerns the interface to expect from IPFS implementations. This interface is a currently active endeavor - expect it to be complete in the next few weeks (August 2016). You can use it today to consult the methods available.
Adding to the methods defined by interface-ipfs-core, js-ipfs-api exposes a set of extra utility methods. These utility functions are scoped behind the ipfs.util.
Complete documentation for these methods is coming with: ipfs-inactive#305
ipfs.util.addFromFs(path, option, callback)
Reads a file from path on the filesystem and adds it to IPFS. If path is a directory, use option { recursive: true } to add the directory and all its sub-directories.
ipfs.util.addFromFs('path/to/a/file', { recursive: true }, (err, result) => {
if (err) {
throw err
}
console.log(result)
})result is an array of objects describing the files that were added, such as:
[{
path: 'test-folder',
hash: 'QmRNjDeKStKGTQXnJ2NFqeQ9oW23WcpbmvCVrpDHgDg3T6',
size: 2278
},
// ...
]
ipfs.util.addFromURL(url, callback)
ipfs.util.addFromURL('http://example.com/', (err, result) => {
if (err) {
throw err
}
console.log(result)
})
ipfs.util.addFromStream(stream, callback)
This is very similar to ipfs.files.add({path:'', content: stream}). It is like the reverse of cat
ipfs.util.addFromStream(<readable-stream>, (err, result) => {
if (err) {
throw err
}
console.log(result)
})If you do not pass in a callback all API functions will return a Promise. For example:
ipfs.id()
.then(function (id) {
console.log('my id is: ', id)
})
.catch(function(err) {
console.log('Fail: ', err)
})This relies on a global Promise object. If you are in an environment where that is not
yet available you need to bring your own polyfill.
We run tests by executing npm test in a terminal window. This will run both Node.js and Browser tests, both in Chrome and PhantomJS. To ensure that the module conforms with the interface-ipfs-core spec, we run the batch of tests provided by the interface module, which can be found here.
The js-ipfs-api is a work in progress. As such, there's a few things you can do right now to help out:
- Check out the existing issues!
- Perform code reviews. More eyes will help a) speed the project along b) ensure quality and c) reduce possible future bugs.
- Add tests. There can never be enough tests. Note that interface tests exist inside
interface-ipfs-core. - Contribute to the FAQ repository with any questions you have about IPFS or any of the relevant technology. A good example would be asking, 'What is a merkledag tree?'. If you don't know a term, odds are, someone else doesn't either. Eventually, we should have a good understanding of where we need to improve communications and teaching together to make IPFS and IPN better.
Want to hack on IPFS?
This module started as a direct mapping from the go-ipfs cli to a JavaScript implementation, although this was useful and familiar to a lot of developers that were coming to IPFS for the first time, it also created some confusion on how to operate the core of IPFS and have access to the full capacity of the protocol. After much consideration, we decided to create interface-ipfs-core with the goal of standardizing the interface of a core implementation of IPFS, and keep the utility functions the IPFS community learned to use and love, such as reading files from disk and storing them directly to IPFS.