Add initial wasm32-wasi support #416
Conversation
This is also the groundwork needed to make a web version of ruff debug fails in wasmtime with "too many locals: locals exceed maximum", so release only atm. Usage: Either ``` cargo build --target wasm32-wasi --release --no-default-features wasmtime run --dir . ~/ruff/target/wasm32-wasi/release/ruff.wasm . ``` or with latest main maturin: ``` maturin build --target wasm32-wasi --release --strip --no-default-features pip install target/wheels/ruff-0.0.69-py3-none-any.whl ruff . # Currenly limit to . due to wasi isolation ```
|
This is awesome. I did basic |
| @@ -1,10 +1,17 @@ | |||
| // cacache uses asyncd-std which has no wasm support, so currently no caching support on wasm | |||
There was a problem hiding this comment.
Could we instead (or in addition) avoid calling into cache at all when target_family = "wasm"?
There was a problem hiding this comment.
done; i'd keep compiling cache.rs on wasm though because caching there should be possible (either in cwd like pytest or to some extent in local storage), it's just cacache that is inactive and hasn't completed tokio support (zkat/cacache-rs#29)
|
The |
charliermarsh
force-pushed
the
main
branch
6 times, most recently
from
a69cce1
to
3ab1cfc
Compare
I'm currently experimenting whether it's feasible to make wasm32-wasi wheels. This is also the groundwork needed to make a web version of ruff, which might the more interesting use case.
Debug fails in wasmtime with "too many locals: locals exceed maximum", so release only atm.
Usage:
Either
or with latest main maturin
I hope that magiclen/path-absolutize#12 lands soon so i can switch back to crates.io path-absolutize before this gets merged