Status

Tracking issue: https://github.com/ipfs/ipfs-blog/issues/445

Below is in-progress proposed blog entry that @Steve (biglep) wants to get out out in 202207 202209 202211. It is related to conversations had at ‣. It may not make sense as a blog post in its current form. For the purposes of Lab Week and IPFS Camp in 202210, it has functioned more as a way to get out on paper current thinking about our JS stack.

• 202207 - Initial sketching of what want to cover and started on the outline
• 2022-09-02 - Filled in more of the outline to make it easier to collaborate with @Daniel Norman. @Steve (biglep) don’t the flow is quite right though. This is as far as could get to in 30 minute timebox.
• 2022-10-19 - Wrote out the content that want to get across from Key points want to get across so can get more meaningful feedback.
• 2022-10-26 - Multiple rounds of feedback and updating during Lab Week. This is now ready to moved to a PR in GitHub.
• 2022-10-27 - Published: https://blog.ipfs.tech/state-of-ipfs-in-js/

Key points want to get across

These are not listed in a particular order, but I want to hit these points:

• [x] What the team has been up to (TypeScript, ESM, js-libp2p)
• [x] js-ipfs does have a DHT implementation
• [x] There are various access patterns to using JS.
• [x] js-kubo-rpc-client is what should be used if you want to interface with Kubo.
• [x] We are decoupling JS developments from the Kubo and its RPC API.
• [x] More transports are coming to js-libp2p which will change the connectivity story.
• [x] Preload nodes will be shutting down
• [x] New names are coming