You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using --features as the last argument to wasm-pack does not get treated as an extra option that is passed to cargo build but an error -
$ wasm-pack build --release --target web --features wasm
error: Found argument '--features' which wasn't expected, or isn't valid in this context
USAGE:
wasm-pack build --release --target <target>
For more information try --help
🤔 Expected Behavior
The build command can pass extra options straight to cargo build even if they are not supported in wasm-pack. To use them simply add the extra arguments at the very end of your command, just as you would for cargo build. For example, to build the previous example using cargo's offline feature:
$ wasm-pack build --release --target web --features wasm
error: Found argument '--features' which wasn't expected, or isn't valid in this context
USAGE:
wasm-pack build --release --target <target>
For more information try --help
🌍 Your environment
Include the relevant details of your environment.
wasm-pack version: 0.10.1
rustc version: 1.54.0 (a178d0322 2021-07-26)
The text was updated successfully, but these errors were encountered:
🐛 Bug description
Using
--features
as the last argument towasm-pack
does not get treated as an extra option that is passed tocargo build
but an error -🤔 Expected Behavior
The build command can pass extra options straight to cargo build even if they are not supported in wasm-pack. To use them simply add the extra arguments at the very end of your command, just as you would for cargo build. For example, to build the previous example using cargo's offline feature:
https://rustwasm.github.io/wasm-pack/book/commands/build.html#extra-options
👟 Steps to reproduce
🌍 Your environment
Include the relevant details of your environment.
wasm-pack version: 0.10.1
rustc version: 1.54.0 (a178d0322 2021-07-26)
The text was updated successfully, but these errors were encountered: