-
Notifications
You must be signed in to change notification settings - Fork 5
feat: build on wasm #75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
817309b to
42d921f
Compare
|
Documentation for this PR has been generated and is available at: https://n0-computer.github.io/iroh-docs/pr/75/docs/iroh_docs/ Last updated: 2025-11-11T22:58:19Z |
dfd62c8 to
061ece7
Compare
|
I've taken the liberty of updating this PR, all of the upstream PRs this one depends on are now merged, we're only waiting on a release for n0-future that'll include the features this relies on. |
|
n0-future 0.3.1 is released now ✌️ |
|
Updated to use the n0-future release. I think this is ready for merge now :) |
|
TIL if you import Pushed what is hopefully a fix, but ideally we'd have a CI check that ensures we use the |
|
speaking of references to |
Description
Make iroh-docs work in WebAssembly in the browser, memstore only.
n0-futurefor time and tasks.redbworks in-memory in the browser. No persistent store for now. In native environments, we spawn a separate thread for the storage actor with a single-threaded tokio runtime. In wasm, we instead simply run this on the main thread. With the inmemory store this is fine, IMO.Replicaare now async because we previously usedsend_blockingon aasync_channel::Sender(uuh) andasync_channel::Sender::send_blockingis not available on wasm.Breaking Changes
Made a couple of methods on
Replicaasync because we previously usedsend_blockingon aasync_channel::Sender(uuh) andasync_channel::Sender::send_blockingis not available on wasm. This is a much needed refactor anyways.(needs more details)
Notes & open questions
Change checklist