-
Notifications
You must be signed in to change notification settings - Fork 409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't force usage of the nightly toolchain #289
Comments
sounds good to me! would we want ways to manually override as well? we ended up forcing nightly because people with strange setups were sometimes running into issues where another toolchain ended up getting used. i don't feel strongly about it and i think it's a good idea to make it more flexible as the edition approaches! |
I think long term we'd probably want to avoid toolchain management entirely in the sense of just inheriting what the user has already configured. In the short-term though |
I've been very confused for the past hour or so because To fix, I just had to |
closing in favor of #351 |
For future reference of absolute beginners: I got here because I was trying to compile some stuff that required the nightly toolchain but wasm-pack wasn't using it. I ended up installing and setting the nightly toolchain as the default and running
|
💡 Feature description
Currently wasm-pack will automatically switch to (and download if necessary) the nightly toolchain, but the upcoming 1.30.0 release will support
wasm-bindgen
andwasm-pack
on stable. It'd be great if, while 1.30.0 is in beta, we could also test out beta!One idea could be to perhaps look at rustc's current version and automatically switch to nightly if it's less than 1.30.0 and otherwise use it as-is if it's 1.30.0+
The text was updated successfully, but these errors were encountered: