js-libp2p 0.27 released

by Jacob Heun on 2020-02-07

It’s heeeeere! After a very long road, and a lot of lessons learned, the Async Await refactor of js-libp2p has landed in the 0.27 release. If you’re not familiar with the refactor you can read up more about the reasons and history in a recent blog post by the wonderful Alan Shaw, The Async Await Refactor. In addition to the efforts mentioned there, the refactor to js-libp2p includes a slew of additional improvements, the highlights of which you can read about below.

In addition to these highlights, we’ve consolidated many of the core modules of js-libp2p into js-libp2p itself in an effort to make it easier for community members to contribute. We’ve also consolidated our interface repositories into libp2p/js-interfaces and improved the documentation and test suites there.

And a wonderful bonus, we’ve measured memory usage improvements between 30-40% compared to the previous version, 0.26!

We’re really excited for 2020 and the opportunities this HUGE effort has opened for js-libp2p, and we’re looking forward to making it even better!

🔦 Highlights

📜 Improved docs

We’ve done an overhaul of our docs to make libp2p easier to use. Among other docs in the new doc folder, you can find a full list of exposed methods in the API.md, and a guide on how to configure libp2p in CONFIGURATION.md. We’ve also created a Getting Started guide for anyone starting out with libp2p.

⌚️ Async/Await instead of Callbacks

All callback APIs have been changed to be async / await compliant. See the API.md readme for detailed usage. When migrating, you can leverage the migration guide to see samples on some of the common migrations you may need to make.

🚰 Streaming Iterables instead of Pull Streams

Now that readable streams are async iterable, we can leverage Streaming Iterables instead of Pull Streams to greatly simplify the internal stream logic of libp2p. Among other things, this makes debugging streams much easier. You can check out the it-awesome repo for a list of an increasing number of modules built for the streaming iterables ecosystem. This also includes modules to convert to and from pull streams if you need to refactor your applications over time. If you’re having trouble migrating, please feel free to reach out on the discuss forums!

📞 Clearer Connections

We’ve created a whole new Connection Interface! Creating multiple streams off of a single connection is now much clearer, and every stream created is tracked in the Connection. This makes it much easier to keep track of every open stream, which greatly empowers resource management in js-libp2p.

// Was
libp2p.dialProtocol(remotePeerInfo, protocol, (error, stream) => { })

// Now
const connection = await libp2p.dial(remotePeerInfo)
const { stream, protocol } = await connection.newStream(protocols)
const allStreams = connection.streams

⏹ Abortable Dials

We’ve reconstructed transports and connections from the ground up. This gives us the ability to pass an AbortSignal when dialing, so we can now properly terminate connections early. This also means we’ll be able to add proper support for parallel dials to reduce connection times without running the risk of lingering dials.

const controller = new AbortController()
libp2p.dial(remotePeerInfo, { signal: controller.signal })
// after a short delay...
controller.abort()

🆔 The Identify Push Protocol

Identify Push is now available in js-libp2p. As a libp2p node changes its Multiaddrs (changes in networks) or protocols, it will broadcast those changes to all connected peers. Once support for AutoNAT and AutoRelay is added to js-libp2p, we will be able to broadcast those changes maximizing the effectiveness of those protocols.

🔍 Plaintext 2 for testing

We’ve upgraded from Plaintext 1 to 2. If you need to test things locally without encryption to see what’s going on over the wire, Plaintext 2 makes this more viable. Public Keys are now exchanged, which is required by many protocols. This should NEVER be used in production, happy testing!

🙏 More polite connections

Currently when two nodes connect, they will actively ask each other what protocols they support. This ends up being multiple checks in parallel, rather than getting the information from a single Identify check. js-libp2p will now only use Identify. This greatly reduces network chatter. The peerStore, formerly peerBook to better match common libp2p terminology, will now emit change events for protocols. Applications that need to check for protocol support can now politely listen for updates, instead of actively checking every peer that connects.

libp2p.peerStore.on('change:protocols', ({ peerInfo, protocols }) => { ... })

📊 Metrics (formerly Stats) can now be enabled/disabled

We’re making stats disabled by default and they are now available at libp2p.metrics instead of libp2p.stats. You can enable metrics if you need them, but for performance reasons we have disabled them by default. Good news, if you need to run them they’re more performant as we’ve moved away from event emitting in metrics. This greatly reduces the amount of processing that happens until you explicitly request something! You can read more about Metrics at METRICS.md.

🏗 API Changes

See the API.md readme for detailed usage on the new API. Significant breaking changes are detailed below.

❤️ Huge thank you to everyone that made this release possible

In alphabetical order, here are the 60 humans that made 1241 contributions to this release:

🙌🏽 Want to contribute?

Would you like to contribute to the libp2p project and don’t know how? Well, there are a few places you can get started:

⁉️ Do you have questions?

The best place to ask your questions about libp2p, how it works and what you can do with it is at discuss.libp2p.io. We are also available at the #libp2p channel on Freenode.

Comments