Project status - Alpha

We've come a long way, but this project is still in Alpha, lots of development is happening, API might change, beware of the Dragons 🐉..

Want to get started? Check our examples folder to learn how to spawn an IPFS node in Node.js and in the Browser.

You can check the development status at the Kanban Board.

Please read this: The DHT, a fundamental piece for automatic content and peer discovery is not yet complete. There are multiple applications that can be built without this service but nevertheless it is fundamental to getting that magic IPFS experience. The current status is that implementation is done and merged and we're working on performance issues. Expect the DHT to be available in a release very soon.

Weekly Core Dev Calls

Tech Lead

David Dias

Lead Maintainer

Alan Shaw

Table of Contents

• Install
  • npm
  • Use in Node.js
  • Through command line tool
  • Use in the browser
• Usage
  • IPFS CLI
  • IPFS Daemon
  • IPFS Module (use IPFS as a module in Node.js or in the Browser)
  • Tutorials and Examples
  • API Docs
    • Constructor
    • Events
    • start
    • stop
    • Core API
      • Files
      • Graph
      • Name
      • Crypto and Key Management
      • Network
      • Node Management
    • Static types and utils
• FAQ
• Running js-ipfs with Docker
• Packages
• Development
  • Clone and install dependencies
  • Run Tests
  • Lint
  • Build a dist version
• Contribute
  • Want to hack on IPFS?
• License

Install

npm

This project is available through npm. To install, run:

> npm install ipfs

JS IPFS depends on native modules that are installed by node-gyp. If you have problems running the command above, it is likely that the build tools required by node-gyp are missing from your system. Please install them and then try again.

We support both the Current and Active LTS versions of Node.js. Please see nodejs.org for what these currently are.

This project is tested on macOS, Linux and Windows.

Use in Node.js

To create an IPFS node programmatically:

const IPFS = require('ipfs')
const node = new IPFS()

node.on('ready', () => {
  // Ready to use!
  // See https://github.com/ipfs/js-ipfs#core-api
})

Through command line tool

In order to use js-ipfs as a CLI, you must install it with the global flag. Run the following (even if you have ipfs installed locally):

npm install ipfs --global

The CLI is available by using the command jsipfs in your terminal. This is aliased, instead of using ipfs, to make sure it does not conflict with the Go implementation.

Use in the browser

Learn how to bundle with browserify and webpack in the examples folder.

You can also load it using a <script> using the unpkg CDN or the jsDelivr CDN. Inserting one of the following lines will make a Ipfs object available in the global namespace.

<!-- loading the minified version -->
<script src="https://unpkg.com/ipfs/dist/index.min.js"></script>
<script src="https://cdn.jsdelivr.net/npm/ipfs/dist/index.min.js"></script>

<!-- loading the human-readable (not minified) version -->
<script src="https://unpkg.com/ipfs/dist/index.js"></script>
<script src="https://cdn.jsdelivr.net/npm/ipfs/dist/index.js"></script>

Inserting one of the above lines will make an Ipfs object available in the global namespace:

<script>
const node = new window.Ipfs()

node.on('ready', () => {
  // Ready to use!
  // See https://github.com/ipfs/js-ipfs#core-api
})
</script>

Usage

IPFS CLI

The jsipfs CLI, available when js-ipfs is installed globally, follows(should, it is a WIP) the same interface defined by go-ipfs, you can always use the help command for help menus.

# Install js-ipfs globally
> npm install ipfs --global
> jsipfs --help
Commands:
  bitswap               A set of commands to manipulate the bitswap agent.
  block                 Manipulate raw IPFS blocks.
  bootstrap             Show or edit the list of bootstrap peers.
  commands              List all available commands
  config <key> [value]  Get and set IPFS config values
  daemon                Start a long-running daemon process
# ...

js-ipfs uses some different default config values, so that they don't clash directly with a go-ipfs node running in the same machine. These are:

• default repo location: ~/.jsipfs (can be changed with env variable IPFS_PATH)
• default swarm port: 4002
• default API port: 5002

IPFS Daemon

The IPFS Daemon exposes the API defined http-api-spec. You can use any of the IPFS HTTP-API client libraries with it, such as: js-ipfs-http-client.

If you want a programmatic way to spawn a IPFS Daemon using JavaScript, check out ipfsd-ctl module

IPFS Module

Use the IPFS Module as a dependency of a project to spawn in process instances of IPFS. Create an instance by calling new IPFS() and waiting for its ready event:

// Create the IPFS node instance
const node = new IPFS()

node.on('ready', () => {
  // Your node is now ready to use \o/

  // stopping a node
  node.stop(() => {
    // node is now 'offline'
  })
})

Tutorials and Examples

You can find some examples and tutorials in the examples folder, these exist to help you get started using js-ipfs.

API

IPFS Constructor

const node = new IPFS([options])

Creates and returns an instance of an IPFS node. Use the options argument to specify advanced configuration. It is an object with any of these properties:

options.repo

| Type | Default | |------|---------| | string or ipfs.Repo instance | '~/.jsipfs' in Node.js, 'ipfs' in browsers |

The file path at which to store the IPFS node’s data. Alternatively, you can set up a customized storage system by providing an ipfs.Repo instance.

Example:

// Store data outside your user directory
const node = new IPFS({ repo: '/var/ipfs/data' })

options.init

| Type | Default | |------|---------| | boolean or object | true |

Initialize the repo when creating the IPFS node.

If you have already initialized a repo before creating your IPFS node (e.g. you are loading a repo that was saved to disk from a previous run of your program), you must make sure to set this to false. Note that initializing a repo is different from creating an instance of ipfs.Repo. The IPFS constructor sets many special properties when initializing a repo, so you should usually not try and call repoInstance.init() yourself.

Instead of a boolean, you may provide an object with custom initialization options. All properties are optional:

• emptyRepo (boolean) Whether to remove built-in assets, like the instructional tour and empty mutable file system, from the repo. (Default: false)
• bits (number) Number of bits to use in the generated key pair. (Default: 2048)
• privateKey (string/PeerId) A pre-generated private key to use. Can be either a base64 string or a PeerId instance. NOTE: This overrides bits.

  // Generating a Peer ID:
  const PeerId = require('peer-id')
  PeerId.create({ bits: 2048 }, (err, peerId) => {
    // Generates a new Peer ID, complete with public/private keypair
    // See https://github.com/libp2p/js-peer-id
  })

• pass (string) A passphrase to encrypt keys. You should generally use the top-level pass option instead of the init.pass option (this one will take its value from the top-level option if not set).

options.start

| Type | Default | |------|---------| | boolean | true |

If false, do not automatically start the IPFS node. Instead, you’ll need to manually call node.start() yourself.

options.pass

| Type | Default | |------|---------| | string | null |

A passphrase to encrypt/decrypt your keys.

options.silent

| Type | Default | |------|---------| | Boolean | false |

Prevents all logging output from the IPFS node.

options.relay

| Type | Default | |------|---------| | object | { enabled: true, hop: { enabled: false, active: false } } |

Configure circuit relay (see the circuit relay tutorial to learn more).

• enabled (boolean): Enable circuit relay dialer and listener. (Default: true)
• hop (object)
  • enabled (boolean): Make this node a relay (other nodes can connect through it). (Default: false)
  • active (boolean): Make this an active relay node. Active relay nodes will attempt to dial a destination peer even if that peer is not yet connected to the relay. (Default: false)

options.preload

| Type | Default | |------|---------| | object | { enabled: true, addresses: [...] } |

Configure remote preload nodes. The remote will preload content added on this node, and also attempt to preload objects requested by this node.

• enabled (boolean): Enable content preloading (Default: true)
• addresses (array): Multiaddr API addresses of nodes that should preload content. NOTE: nodes specified here should also be added to your node's bootstrap address list at config.Boostrap.

options.EXPERIMENTAL

| Type | Default | |------|---------| | object | { pubsub: false, sharding: false, dht: false } |

Enable and configure experimental features.

• pubsub (boolean): Enable libp2p pub-sub. (Default: false)
• ipnsPubsub (boolean): Enable pub-sub on IPNS. (Default: false)
• sharding (boolean): Enable directory sharding. Directories that have many child objects will be represented by multiple DAG nodes instead of just one. It can improve lookup performance when a directory has several thousand files or more. (Default: false)

options.config

| Type | Default | |------|---------| | object | config-nodejs.js in Node.js, config-browser.js in browsers |

Modify the default IPFS node config. This object will be merged with the default config; it will not replace it.

options.libp2p

| Type | Default | |------|---------| | object | libp2p-nodejs.js in Node.js, libp2p-browser.js in browsers | | function | libp2p bundle |

The libp2p option allows you to build your libp2p node by configuration, or via a bundle function. If you are looking to just modify the below options, using the object format is the quickest way to get the default features of libp2p. If you need to create a more customized libp2p node, such as with custom transports or peer/content routers that need some of the ipfs data on startup, a custom bundle is a great way to achieve this.

You can see the bundle in action in the custom libp2p example.

• modules (object):
  • transport (Array<libp2p.Transport>): An array of Libp2p transport classes/instances to use instead of the defaults. See libp2p/interface-transport for details.
  • peerDiscovery (Array<libp2p.PeerDiscovery>): An array of Libp2p peer discovery classes/instances to use instead of the defaults. See libp2p/peer-discovery for details. If passing a class, configuration can be passed using the config section below under the key corresponding to you module's unique tag (a static property on the class)
• config (object):
  • peerDiscovery (object):
    • autoDial (boolean): Dial to discovered peers when under the Connection Manager min peer count watermark. (default true)
    • [PeerDiscovery.tag] (object): configuration for a peer discovery module
      • enabled (boolean): whether this module is enabled or disabled
      • [custom config] (any): other keys are specific to the module
  • dht (object): Configuration options for the DHT (WARNING: the current DHT implementation has performance issues, your mileage may vary)
    • enabled (boolean): whether the DHT is enabled or not (default false)
    • kBucketSize (number): bucket size (default 20)
    • randomWalk (object): configuration for random walk
      • enabled (boolean): whether random DHT walking is enabled (default false)

options.connectionManager

| Type | Default | |------|---------| | object | defaults |

Configure the libp2p connection manager.

Events

IPFS instances are Node.js EventEmitters. You can listen for events by calling node.on('event', handler):

const node = new IPFS({ repo: '/var/ipfs/data' })
node.on('error', errorObject => console.error(errorObject))

• error is always accompanied by an Error object with information about the error that occurred.

  node.on('error', error => {
    console.error(error.message)
  })

• init is emitted after a new repo has been initialized. It will not be emitted if you set the init: false option on the constructor.

• ready is emitted when a node is ready to use. This is the final event you will receive when creating a node (after init and start).

  When creating a new IPFS node, you should almost always wait for the ready event before calling methods or interacting with the node.

• start is emitted when a node has started listening for connections. It will not be emitted if you set the start: false option on the constructor.

• stop is emitted when a node has closed all connections and released access to its repo. This is usually the result of calling node.stop().

node.start([callback])

Start listening for connections with other IPFS nodes on the network. In most cases, you do not need to call this method — new IPFS() will automatically do it for you.

This method is asynchronous. There are several ways to be notified when the node has finished starting:

1. If you call node.start() with no arguments, it returns a promise.

   const node = new IPFS({ start: false })
   
   node.on('ready', async () => {
     console.log('Node is ready to use!')
   
     try {
       await node.start()
       console.log('Node started!')
     } catch (error) {
       console.error('Node failed to start!', error)
     }
   })

2. If you pass a function as the final argument, it will be called when the node is started (Note: this method will not return a promise if you use a callback function).

   const node = new IPFS({ start: false })
   
   node.on('ready', () => {
     console.log('Node is ready to use!')
   
     node.start(error => {
       if (error) {
         return console.error('Node failed to start!', error)
       }
       console.log('Node started!')
     })
   })

3. You can listen for the start event.

   const node = new IPFS({ start: false })
   
   node.on('ready', () => {
     console.log('Node is ready to use!')
     node.start()
   })
   
   node.on('error', error => {
     console.error('Something went terribly wrong!', error)
   })
   
   node.on('start', () => console.log('Node started!'))

node.stop([callback])

Close and stop listening for connections with other IPFS nodes, then release access to the node’s repo.

This method is asynchronous. There are several ways to be notified when the node has completely stopped:

1. If you call node.stop() with no arguments, it returns a promise.

   const node = new IPFS()
   
   node.on('ready', async () => {
     console.log('Node is ready to use!')
   
     try {
       await node.stop()
       console.log('Node stopped!')
     } catch (error) {
       console.error('Node failed to stop cleanly!', error)
     }
   })

2. If you pass a function as the final argument, it will be called when the node is stopped (Note: this method will not return a promise if you use a callback function).

   const node = new IPFS()
   
   node.on('ready', () => {
     console.log('Node is ready to use!')
   
     node.stop(error => {
       if (error) {
         return console.error('Node failed to stop cleanly!', error)
       }
       console.log('Node stopped!')
     })
   })

3. You can listen for the stop event.

   const node = new IPFS()
   
   node.on('ready', () => {
     console.log('Node is ready to use!')
     node.stop()
   })
   
   node.on('error', error => {
     console.error('Something went terribly wrong!', error)
   })
   
   node.on('stop', () => console.log('Node stopped!'))

Core API

The IPFS core API provides all functionality that is not specific to setting up and starting or stopping a node. This API is available directly on an IPFS instance, on the command line (when using the CLI interface), and as an HTTP REST API. For a complete reference, see .

The core API is grouped into several areas:

Files

• Regular Files API
  • ipfs.add(data, [options], [callback])
  • ipfs.addPullStream([options])
  • ipfs.addReadableStream([options])
  • ipfs.addFromStream(stream, [callback])
  • ipfs.addFromFs(path, [options], [callback])
  • ipfs.addFromUrl(url, [options], [callback])
  • ipfs.cat(ipfsPath, [options], [callback])
  • ipfs.catPullStream(ipfsPath, [options])
  • ipfs.catReadableStream(ipfsPath, [options])
  • ipfs.get(ipfsPath, [options], [callback])
  • ipfs.getPullStream(ipfsPath, [options])
  • ipfs.getReadableStream(ipfsPath, [options])
  • ipfs.ls(ipfsPath, [callback])
  • ipfs.lsPullStream(ipfsPath)
  • ipfs.lsReadableStream(ipfsPath)
• MFS (mutable file system) specific
  • ipfs.files.cp([from, to], [callback])
  • ipfs.files.flush([path], [callback])
  • ipfs.files.ls([path], [options], [callback])
  • ipfs.files.mkdir(path, [options], [callback])
  • ipfs.files.mv([from, to], [callback])
  • ipfs.files.read(path, [options], [callback])
  • ipfs.files.readPullStream(path, [options])
  • ipfs.files.readReadableStream(path, [options])
  • ipfs.files.rm(path, [options], [callback])
  • ipfs.files.stat(path, [options], [callback])
  • ipfs.files.write(path, content, [options], [callback])

Graph

• dag

  • ipfs.dag.put(dagNode, [options], [callback])
  • ipfs.dag.get(cid, [path], [options], [callback])
  • ipfs.dag.tree(cid, [path], [options], [callback])

• pin

  • ipfs.pin.add(hash, [options], [callback])
  • ipfs.pin.ls([hash], [options], [callback])
  • ipfs.pin.rm(hash, [options], [callback])

• object (legacy)

  • ipfs.object.new([template], [callback])
  • ipfs.object.put(obj, [options], [callback])
  • ipfs.object.get(multihash, [options], [callback])
  • ipfs.object.data(multihash, [options], [callback])
  • ipfs.object.links(multihash, [options], [callback])
  • ipfs.object.stat(multihash, [options], [callback])
  • ipfs.object.patch.addLink(multihash, DAGLink, [options], [callback])
  • ipfs.object.patch.rmLink(multihash, DAGLink, [options], [callback])
  • ipfs.object.patch.appendData(multihash, data, [options], [callback])
  • ipfs.object.patch.setData(multihash, data, [options], [callback])

Block

• block
  • ipfs.block.get(cid, [options], [callback])
  • ipfs.block.put(block, cid, [callback])
  • ipfs.block.stat(cid, [callback])
• bitswap
  • ipfs.bitswap.wantlist([peerId], [callback])
  • ipfs.bitswap.stat([callback])

Name

• name
  • ipfs.name.publish(value, [options], [callback])
  • ipfs.name.pubsub.cancel(arg, [callback])
  • ipfs.name.pubsub.state([callback])
  • ipfs.name.pubsub.subs([callback])
  • ipfs.name.resolve(value, [options], [callback])

Crypto and Key Management

• key

  • ipfs.key.export(name, password, [callback])
  • ipfs.key.gen(name, options, [callback])
  • ipfs.key.import(name, pem, password, [callback])
  • ipfs.key.list([callback])
  • ipfs.key.rename(oldName, newName, [callback])
  • ipfs.key.rm(name, [callback])

• crypto (not implemented yet)

Network

• bootstrap

  • ipfs.bootstrap.list([callback])
  • ipfs.bootstrap.add(addr, [options], [callback])
  • ipfs.bootstrap.rm(peer, [options], [callback])

• dht

  • ipfs.dht.findPeer(peerId, [callback])
  • ipfs.dht.findProvs(multihash, [callback])
  • ipfs.dht.get(key, [callback])
  • ipfs.dht.provide(cid, [callback])
  • ipfs.dht.put(key, value, [callback])
  • ipfs.dht.query(peerId, [callback])

• pubsub

  • ipfs.pubsub.subscribe(topic, handler, [options], [callback])
  • ipfs.pubsub.unsubscribe(topic, handler, [callback])
  • ipfs.pubsub.publish(topic, data, [callback])
  • ipfs.pubsub.ls(topic, [callback])
  • ipfs.pubsub.peers(topic, [callback])

• libp2p. Every IPFS instance also exposes the libp2p SPEC at ipfs.libp2p. The formal interface for this SPEC hasn't been defined but you can find documentation at its implementations:

  • Node.js bundle
  • Browser Bundle
  • libp2p baseclass

• swarm

  • ipfs.swarm.addrs([callback])
  • ipfs.swarm.connect(addr, [callback])
  • ipfs.swarm.disconnect(addr, [callback])
  • ipfs.swarm.peers([options], [callback])

Node Management

• miscellaneous operations

  • ipfs.id([callback])
  • ipfs.version([callback])
  • ipfs.ping(peerId, [options], [callback])
  • ipfs.pingReadableStream(peerId, [options])
  • ipfs.pingPullStream(peerId, [options])
  • ipfs.init([options], [callback])
  • ipfs.start([callback])
  • ipfs.stop([callback])
  • ipfs.isOnline()
  • ipfs.resolve(name, [options], [callback])
  • ipfs.dns(name, [options], [callback]

• repo

  • ipfs.repo.init
  • ipfs.repo.stat([options], [callback])
  • ipfs.repo.version([callback])
  • ipfs.repo.gc([options], [callback]) (not implemented yet)

• stats

  • ipfs.stats.bitswap([callback])
  • ipfs.stats.bw([options], [callback])
  • ipfs.stats.bwPullStream([options]) -> Pull Stream
  • ipfs.stats.bwReadableStream([options]) -> Readable Stream
  • ipfs.stats.repo([options], [callback])

• config

  • ipfs.config.get([key], [callback])
  • ipfs.config.set(key, value, [callback])
  • ipfs.config.replace(config, [callback])

Static types and utils

Aside from the default export, ipfs exports various types and utilities that are included in the bundle:

• crypto
• isIPFS
• Buffer
• PeerId
• PeerInfo
• multiaddr
• multibase
• multihash
• multihashing
• multicodec
• CID

These can be accessed like this, for example:

const { CID } = require('ipfs')
// ...or from an es-module:
import { CID } from 'ipfs'

FAQ

How to enable WebRTC support for js-ipfs in the Browser

To add a WebRTC transport to your js-ipfs node, you must add a WebRTC multiaddr. To do that, simple override the config.Addresses.Swarm array which contains all the multiaddrs which the IPFS node will use. See below:

const node = new IPFS({
  config: {
    Addresses: {
      Swarm: [
        '/dns4/wrtc-star.discovery.libp2p.io/tcp/443/wss/p2p-webrtc-star'
      ]
    }
  }
})

node.on('ready', () => {
  // your instance with WebRTC is ready
})

Important: This transport usage is kind of unstable and several users have experienced crashes. Track development of a solution at https://github.com/ipfs/js-ipfs/issues/1088.

Is there WebRTC support for js-ipfs with Node.js?

Yes, however, bear in mind that there isn't a 100% stable solution to use WebRTC in Node.js, use it at your own risk. The most tested options are:

• wrtc - Follow the install instructions.
• electron-webrtc

To add WebRTC support in a IPFS node instance, do:

const wrtc = require('wrtc') // or require('electron-webrtc')()
const WStar = require('libp2p-webrtc-star')
const wstar = new WStar({ wrtc })

const node = new IPFS({
  repo: 'your-repo-path',
  // start: false,
  config: {
    Addresses: {
      Swarm: [
        "/ip4/0.0.0.0/tcp/4002",
        "/ip4/127.0.0.1/tcp/4003/ws",
        "/dns4/wrtc-star.discovery.libp2p.io/tcp/443/wss/p2p-webrtc-star"
      ]
    }
  },
  libp2p: {
    modules: {
      transport: [wstar],
      peerDiscovery: [wstar.discovery]
    }
  }
})

node.on('ready', () => {
  // your instance with WebRTC is ready
})

To add WebRTC support to the IPFS daemon, you only need to install one of the WebRTC modules globally:

npm install wrtc --global
# or
npm install electron-webrtc --global

Then, update your IPFS Daemon config to include the multiaddr for this new transport on the Addresses.Swarm array. Add: "/dns4/wrtc-star.discovery.libp2p.io/wss/p2p-webrtc-star"

How can I configure an IPFS node to use a custom signaling endpoint for my WebRTC transport?

You'll need to execute a compatible signaling server (libp2p-webrtc-star works) and include the correct configuration param for your IPFS node:

• provide the multiaddr for the signaling server

const node = new IPFS({
  repo: 'your-repo-path',
  config: {
    Addresses: {
      Swarm: [
        '/ip4/127.0.0.1/tcp/9090/ws/p2p-webrtc-star'
      ]
    }
  }
})

The code above assumes you are running a local signaling server on port 9090. Provide the correct values accordingly.

Is there a more stable alternative to webrtc-star that offers a similar functionality?

Yes, websocket-star! A WebSockets based transport that uses a Relay to route the messages. To enable it, just do:

const node = new IPFS({
  config: {
    Addresses: {
      Swarm: [
        '/dns4/ws-star.discovery.libp2p.io/tcp/443/wss/p2p-websocket-star'
      ]
    }
  }
})

node.on('ready', () => {
  // your instance with websocket-star is ready
})

I see some slowness when hopping between tabs Chrome with IPFS nodes, is there a reason why?

Yes, unfortunately, due to Chrome aggressive resource throttling policy, it cuts freezes the execution of any background tab, turning an IPFS node that was running on that webpage into a vegetable state.

A way to mitigate this in Chrome, is to run your IPFS node inside a Service Worker, so that the IPFS instance runs in a background process. You can learn how to install an IPFS node as a service worker in here the repo ipfs-service-worker

Can I use IPFS in my Electron App?

Yes you can and in many ways. Read https://github.com/ipfs/notes/issues/256 for the multiple options.

If your electron-rebuild step is failing, all you need to do is:

# Electron's version.
export npm_config_target=2.0.0
# The architecture of Electron, can be ia32 or x64.
export npm_config_arch=x64
export npm_config_target_arch=x64
# Download headers for Electron.
export npm_config_disturl=https://atom.io/download/electron
# Tell node-pre-gyp that we are building for Electron.
export npm_config_runtime=electron
# Tell node-pre-gyp to build module from source code.
export npm_config_build_from_source=true
# Install all dependencies, and store cache to ~/.electron-gyp.
HOME=~/.electron-gyp npm install

If you find any other issue, please check the Electron Support issue.

Have more questions?

Ask for help in our forum at https://discuss.ipfs.io or in IRC (#ipfs on Freenode).

Running js-ipfs with Docker

We have automatic Docker builds setup with Docker Hub: https://hub.docker.com/r/ipfs/js-ipfs/

All branches in the Github repository maps to a tag in Docker Hub, except master Git branch which is mapped to latest Docker tag.

You can run js-ipfs like this:

$ docker run -it -p 4002:4002 -p 4003:4003 -p 5002:5002 -p 9090:9090 ipfs/js-ipfs:latest

initializing ipfs node at /root/.jsipfs
generating 2048-bit RSA keypair...done
peer identity: Qmbd5jx8YF1QLhvwfLbCTWXGyZLyEJHrPbtbpRESvYs4FS
to get started, enter:

         jsipfs files cat /ipfs/QmfGBRT6BbWJd7yUc2uYdaUZJBbnEFvTqehPFoSMQ6wgdr/readme

Initializing daemon...
Using wrtc for webrtc support
Swarm listening on /ip4/127.0.0.1/tcp/4003/ws/ipfs/Qmbd5jx8YF1QLhvwfLbCTWXGyZLyEJHrPbtbpRESvYs4FS
Swarm listening on /ip4/172.17.0.2/tcp/4003/ws/ipfs/Qmbd5jx8YF1QLhvwfLbCTWXGyZLyEJHrPbtbpRESvYs4FS
Swarm listening on /ip4/127.0.0.1/tcp/4002/ipfs/Qmbd5jx8YF1QLhvwfLbCTWXGyZLyEJHrPbtbpRESvYs4FS
Swarm listening on /ip4/172.17.0.2/tcp/4002/ipfs/Qmbd5jx8YF1QLhvwfLbCTWXGyZLyEJHrPbtbpRESvYs4FS
API is listening on: /ip4/0.0.0.0/tcp/5002
Gateway (readonly) is listening on: /ip4/0.0.0.0/tcp/9090
Daemon is ready

$ curl --silent localhost:5002/api/v0/id | jq .ID
"Qmbd5jx8YF1QLhvwfLbCTWXGyZLyEJHrPbtbpRESvYs4FS"

Packages

Listing of the main packages used in the IPFS ecosystem. There are also three specifications worth linking here:

• interface-ipfs-core
• http-api-spec
• cli spec

This table is generated using the module package-table with package-table --data=package-list.json.

| Package | Version | Deps | CI/Travis | Coverage | Lead Maintainer | | ---------|---------|---------|---------|---------|--------- | | Files | | ipfs-unixfs-engine | | | | | Alex Potsides | | DAG | | ipld | | | | | Volker Mische | | ipld-dag-pb | | | | | Volker Mische | | ipld-dag-cbor | | | | | Volker Mische | | Repo | | ipfs-repo | | | | | Jacob Heun | | Exchange | | ipfs-block-service | | | | | Volker Mische | | ipfs-bitswap | | | | | Volker Mische | | libp2p | | libp2p | | | | | Jacob Heun | | libp2p-circuit | | | | | Jacob Heun | | libp2p-floodsub | | | | | Vasco Santos | | libp2p-kad-dht | | | | | Vasco Santos | | libp2p-mdns | | | | | Jacob Heun | | libp2p-bootstrap | | | | | Vasco Santos | | libp2p-secio | | | | | Friedel Ziegelmayer | | libp2p-tcp | | | | | Jacob Heun | | libp2p-webrtc-star | | | | | Vasco Santos | | libp2p-websocket-star | | | | | Jacob Heun | | libp2p-websockets | | | | | Jacob Heun | | pull-mplex | | | | | Jacob Heun | | Data Types | | ipfs-block | | | | | Volker Mische | | ipfs-unixfs | | | | | Alex Potsides | | peer-id | | | | | Pedro Teixeira | | peer-info | | | | | Pedro Teixeira | | multiaddr | | | | | Jacob Heun | | multihashes | | | | | David Dias | | Crypto | | libp2p-crypto | | | | | Friedel Ziegelmayer | | libp2p-keychain | | | | | Vasco Santos | | Generics/Utils | | ipfs-http-client | | | | | Alan Shaw | | ipfs-multipart | | | | | N/A | | is-ipfs | | | | | Marcin Rataj | | multihashing | | | | | Hugo Dias | | mafmt | | | | | Vasco Santos |

Development

Clone and install dependencies

> git clone https://github.com/ipfs/js-ipfs.git
> cd js-ipfs
> npm install

Run tests

# run all the unit tests
> npm test

# run individual tests (findprovs)
> npm run test -- --grep findprovs

# run just IPFS tests in Node.js
> npm run test:node

# run just IPFS core tests
> npm run test:node:core

# run just IPFS HTTP-API tests
> npm run test:node:http

# run just IPFS CLI tests
> npm run test:node:cli

# run just IPFS core tests in the Browser (Chrome)
> npm run test:browser

# run some interface tests (block API) on Node.js
> npm run test:node:interface -- --grep '.block'

Run interop tests

Run the interop tests with https://github.com/ipfs/interop

Run benchmark tests

# run all the benchmark tests
> npm run benchmark

# run just IPFS benchmarks in Node.js
> npm run benchmark:node

# run just IPFS benchmarks in Node.js for an IPFS instance
> npm run benchmark:node:core

# run just IPFS benchmarks in Node.js for an IPFS daemon
> npm run benchmark:node:http

# run just IPFS benchmarks in the browser (Chrome)
> npm run benchmark:browser

Lint

Conforming to linting rules is a prerequisite to commit to js-ipfs.

> npm run lint

Build a dist version

> npm run build

Runtime Support

Code Architecture and folder Structure

Source code

> tree src -L 2
src                 # Main source code folder
├── cli             # Implementation of the IPFS CLI
│   └── ...
├── http            # The HTTP-API implementation of IPFS as defined by http-api-spec
├── core            # IPFS implementation, the core (what gets loaded in browser)
│   ├── components  # Each of IPFS subcomponent
│   └── ...
└── ...

Monitoring

The HTTP API exposed with js-ipfs can also be used for exposing metrics about the running js