-
Notifications
You must be signed in to change notification settings - Fork 69
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
Enable riker to build in wasm #151
Comments
I think it's good be able to compile to wasm. But as I see it, the "wasm-bindgen" feature in the Can we make this optional behind our own feature? |
I think that would be the way to do it, yes. Will make a PR tomorrow. |
Any updates on this? |
Ojey, I forgot to do this. Thanks for the reminder! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Trying to get Riker to build in a project using:
cargo build --target=wasm32-unknown-unknown
but it failed with:
I did some quick research and discovered that to enable wasm32 ini uuid, the fix is pretty trivial:
I tested it by locally building riker and also the consuming project. So its a pretty easy win... Thoughts? I can PR if you agree there is no problem with this.
The text was updated successfully, but these errors were encountered: