Open nothingismagick opened 3 years ago
I think it's good be able to compile to wasm. But as I see it, the "wasm-bindgen" feature in the uuid
crate would pull in an additional dependency.
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!
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.