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
Currently, wasm-pack seems to call cargo build with +nightly. This may not be the user's intention, especially in "no-install" mode.
If I'm not mistaken we can set the toolchain using rustup override set nightly immediately after installing it. Then if we installed the toolchain we'll automatically use it in every subsequent command, and if we didn't then whatever goes wrong will be the user's responsibility. :)
If no one objects or gets to it before me I'll submit a pull request.
The text was updated successfully, but these errors were encountered:
itsybitesyspider
changed the title
Don't lock wasm-pack to nightly
Don't lock wasm-pack packages to nightly
Jul 17, 2018
hey @clanehin ! at the moment, wasm-bindgen only works on nightly, so in order to build we'd need nightly still. once the 2018 edition lands, we should be able to move wasm-bindgen to stable, and then i would absolutely be interested in this :)
Currently, wasm-pack seems to call cargo build with +nightly. This may not be the user's intention, especially in "no-install" mode.
If I'm not mistaken we can set the toolchain using
rustup override set nightly
immediately after installing it. Then if we installed the toolchain we'll automatically use it in every subsequent command, and if we didn't then whatever goes wrong will be the user's responsibility. :)If no one objects or gets to it before me I'll submit a pull request.
The text was updated successfully, but these errors were encountered: