What we've been waiting for.

[tomiiide]

This is exactly what we have been looking for at our company, and it's been blocking our upgrade to @solana/kit.

When would there be an npm release?

[GuiBibeau]

Hey @tomiiide! We are in the works of getting a good NPM package name. It's fully experimental, breaking changes likely will happen but i'd love feedback on what is present. I know it's missing a lot but in the next 4-5 days we should get a ton more new features while balancing tree shaking

[tomiiide]

Thanks @GuiBibeau. Great work so far. I have been integrating it into our widget and sdk, and I had to make some changes for our needs.

More feedback.

1. I think the client configuration should have a storage module, so that connector re-connection would be automatically handled inside the library.
2. I also think this PR by @catmcgee is a great direction and would make migration easy for many teams.

Is there a roadmap of the things you plan to add and fix?
How soon do you think a stable version can be released?

[GuiBibeau]

I think the preliminary roadmap looks like this:

React

• Suspense with better support ✅
• re-connection handled automatically
• getting your changes in.
• change cluster
• Refactor to support the new transaction engine of Core (detailed bellow)
• Refactor some "recipes" to use core transaction instructions instead of hard coding in react like now (to support other frameworks too, that won't change the API consumption just the inner working.
• more support for server side helpers in server components

Compatibility package:

• Essentially offer the Connection class but built on top of script. This would offer a form of easy migration for the next 12-18 months while people adopt this new framework. We'll discuss it on web3-compat package #5 but i think we essentially need to support 75% of web3.js connection and that will help people migrate without loosing their mind.

Core:

• swap out the core instruction engine to support a Anza suggestion of transaction planner and executor Not to merge: create a helper lib example anza-xyz/kit#1025
• Bring in some reusable recipes into the new instruction core engine. Eventually these could come from other packages but we need to align with anza to support it
• Generate automated client from IDLs (need to see if this goes in anchor, codama or here)

Node.js/Bun.js package (This is the most unclear yet, i need to talk with folks who use web3.js in the backend to know how they work):

• Parity in "recipes" to the react package
• create and export keypairs to JSON files
• realtime data dumps or ETL support?

Svelte package:

• react feature parity

Vue package:

• React feature parity

Angular package:

• react feature parituy

But to me the real interesting thing is what happens after we get this done. I thing this moves from being a "library" to being a framework above Solana building blocks. Imagine Deploying simply and consuming all sorts of things like an escrow and such here. This is long term plans but i see this as an evolution of the Solana JS approach.

[datasalaryman]

Node.js/Bun.js package ... i need to talk with folks who use web3.js in the backend

An earlier version of https://promisekeepr.xyz used web3.js on both the client (signing) and server side (tx generation, sending and confirming). It's a NextJS implementation run on bun, but I think can also be run on node.

Happy to answer what questions you have.