Fix build on wasm32-unknown-unknown #3367
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
crate-type = "cdylib"
is needed forwasm-pack
to workwasm
feature, everything can be auto-detected (-F wasm
is now a no-op)wasm-bindgen
should only be included forwasm32-unknown-unknown
.wasm32-wasi
does not need it. I'm not sure about emscriptenwasm-pack build
and other commands should now work.--no-default-features
is necessary because thebinaries
feature does not compile on wasm.Note that testing on wasm32-unknown-unknown can't just be done with
cargo test
and requires more work. I'll do that in a separate PR (incl. CI).