Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

⚡️ v0.24.0 RELEASE 🚀 #855

Closed
14 tasks done
daviddias opened this issue May 19, 2017 · 5 comments
Closed
14 tasks done

⚡️ v0.24.0 RELEASE 🚀 #855

daviddias opened this issue May 19, 2017 · 5 comments

Comments

@daviddias
Copy link
Member

daviddias commented May 19, 2017

It is that time when we are ready to cut the next minor release of js-ipfs, isn't that exciting!
🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟🌟

Highlights

👢 WebSockets DNS Bootstrappers by default on the browser

With this release, you won’t need to connect to Bootstrapper nodes manually, they will dialled from the start through their WebSockets endpoints. This also means that we’ve successfully deploy DNS support for multiaddrs, so that you can host your js-ipfs enabled app behind an HTTPS domain and dial to our Bootstrappers through WSS.

🎈WebRTC is now a default transport

We now include WebRTC multiaddr by default on new js-ipfs init calls. This means that both your Node.js and Browser nodes will be able to dial each other using WebRTC and discover other nodes in the network through Signalling Peer Discovery.

Caveat, for Linux/Windows users, due to Node.js wrtc module limited support, you will have to set an environment variable or an Experimental flag to do so, check the README to learn how to do so.

🗺 1st Phase of DHT Implementation Complete

We’ve a working DHT implementation, with this implementation, libp2p got simpler and new PeerRouting and ContentRouting API. We are currently holding this feature behind an Experimental flag until we prune out some interoperability issues with go-ipfs.

🕸 WebWorker and ServiceWorker Support

Now you can run js-ipfs in a WebWorker or a ServiceWorker without encountering any stoppers. We also added a rule to our tests to be run inside a WebWorker to ensure that this feature stays intact.

📶 Better reconnecting handling with WebRTC Transport

You can now switch off your wifi or close your laptop and your js-ipfs node will be able to recover from lost in connectivity graciously.

💅🏽 Refreshed libp2p API

As a byproduct of shipping new features in js-ipfs, js-libp2p got a refreshed API, documentation and examples. Please do check them out and try libp2p at [js-libp2p]

📦 Updated Packages table

Always wondered of how many pieces IPFS is built? Check the updates Packages table at -- https://github.com/ipfs/js-ipfs#packages.

Release checklist

If you would like us to help you with the migration of your js-ipfs enabled app to the newest release, leave us a note on how to run your tests and I'll be happy to try them for you and report things you will need to update in order to migrate.

@daviddias
Copy link
Member Author

This release comes in handy for the new CRDTs on IPFS endeavor and IIIF Viewers with IPFS. If you want to learn more about it check:

You can find a working version and multiple demos and videos, here:

Great work being done by @pgte, @edsilv and @aeschylus 🙌🏽

@daviddias
Copy link
Member Author

Hi @ipfs/javascript-team, just posted the Highlights for this release, let me know if I missed something.

To everyone using js-ipfs, I would really appreciate if you could try this before the release happens and report any problems you might find. If you weren't using any internals directly, you should be golden :)

@daviddias
Copy link
Member Author

daviddias commented May 21, 2017

Run tests on projects using js-ipfs.

Orbit

@haadcode went through the process of testing orbit modules with latest js-ipfs, you can find the results at:

Seems that the modules are still living on v0.22.0

@daviddias
Copy link
Member Author

daviddias commented May 23, 2017

With this release, you can run js-ipfs in a Service Worker \o/

@daviddias
Copy link
Member Author

ipfs@0.24.0 [18:39] Published to npm.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant