Support for wasm32-wasi target?

[iceiix]

Does wasm-pack support building for the new wasm32-wasi target instead of wasm32-unknown-unknown?

I have a project configured to use wasm-pack for wasm32-unknown-unknown, would like to switch to wasm32-wasi, wondering if I have to change the build tool, or if this is not supported and if there is a possibility it may in the future.

I tried wasm-pack build --target wasm32-wasi but this option specifies something else:

    -t, --target <target>        Sets the target environment. [possible values: browser, nodejs, web, no-modules]
                                 [default: browser]

Couldn't find any mention of "wasi" in this repository.

Background: https://github.com/CraneStation/wasmtime/blob/master/docs/WASI-intro.md

[fitzgen]

We don't support wasi yet.

It isn't totally clear what wasm-pack should do with wasi yet. (Not saying it is particularly difficult to figure out, we just haven't discussed it too much yet).

[RReverser]

Just allowing to somehow set target to WASI would be already good. Right now playing with porting some libraries to WASM via wasm-pack, but running into runtime panics due to unimplemented syscalls, which would be solved by passing WASI as a target.

[yurydelendik]

See also https://github.com/rust-lang/cargo/issues/7327

[RReverser]

@yurydelendik Looks like the linked issue has been resolved since.

[yurydelendik]

True. While underline tools are fixed, the wasm-pack code checks and operates only with 'wasm32-unknown-unknown' target.

[RReverser]

Yeah, and seems like at this point it would be a fairly simple fix to allow other targets.