A standalone deployment of a libp2p host, running in its own OS process and installing a set of virtual endpoints to enable co-local applications to: communicate with peers, handle protocols, interact with the DHT, participate in pubsub, etc. no matter the language they are developed in, nor whether a native libp2p implementation exists in that language.
The specs for the daemon are currently housed in the go implementation. You can read them at libp2p/go-libp2p-daemon
npm i -g libp2p-daemon
For a full list of options, you can run help jsp2pd --help.
Running the defaults, jsp2pd, will start the daemon and bind it to a local unix socket path.
Daemon clients will be able to communicate with the daemon over that unix socket.
As an alternative, you can use this daemon with a different version of libp2p as the one specified in package.json. You just need to define its path through an environment variable as follows:
export LIBP2P_JS=./../../js-libp2p/src/index.jsThis module is actively under development. Please check out the issues and submit PRs!
MIT © Protocol Labs