Closed mendess closed 6 months ago
We should document this new feature in the README:
| `wasm-compat` | No | Enables the `getrandom/js` feature. This is necessary for `wasm32-unknown-unknown` targets, when in a JavaScript environment. | ✅ |
wasm32-unknown-unknown?
This target is required for the workers runtime, at least for now. There is experimental WASI support, but we haven't had a chance to test it thoroughly.
We should document this new feature in the README:
| `wasm-compat` | No | Enables the `getrandom/js` feature. This is necessary for `wasm32-unknown-unknown` targets, when in a JavaScript environment. | ✅ |
Docs added
If you're using
prio
from wasm you have to includegetrandom = { version "*", feature = ["js"] }
in your cargo toml, even if you don't make use ofgetrandom
in your code, just so you can activate the "js" feature.I think it would be nicer if prio let me activate the feature without this hack.
Stacked on top of #1058