You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both the Platform trait and the JS bindings are "stable-ish". They don't change too often, but they might occasionally do.
As a side note, I'm pretty convinced that wasm-bindgen is a bad library. We were initially using wasm-bindgen in an earlier prototype of smoldot, and we ditched it because it caused too many issues w.r.t. bundlers and transcripters and all. Keep in mind that the JavaScript world is a huge shitshow, and sooner or later someone will report a weird issue, and if this issue is caused by the internals of wasm-bindgen (which has a high chance of happening), then you will be stuck.
It seems to me that the best solution is for smoldot to re-export some of the code in its Wasm node, and you import it from subtx. However it's not clear to me what exactly and how to do it.
Expose a light client that is wasm compatible to be utilized with subxt.
Smoldot provides an example that interacts with javascript world.
The example relies on the javascript to expose a few core functions (see here).
There are a few ways that this could be approached:
gloo
)substrate-connect
would be a viable / faster optionThe text was updated successfully, but these errors were encountered: