-
Notifications
You must be signed in to change notification settings - Fork 412
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
Distribute wasm-pack binary via cargo #746
Comments
Although it isn't well advertised, you actually can do |
Oh, I see! I think it would be nice to state this on that page as well: https://rustwasm.github.io/wasm-pack/installer/. |
@pablosichert It actually already does, but you have to click on the Maybe we could just always display it, without requiring a click on the link. @ashleygwilliams what do you think? |
i definitely agree that we should not hide the additional installer instrucitons. i would happily accept a pull request for this. i have had an issue open for this for a long time actually: #355 i'm going to close this a duplicate :) |
I don't think this issue is a duplicate of #355. That one is about which install options to display on the website. This issue is about distributing a wasm-pack binary via cargo. Four years ago @Pauan commented that
but I'm not sure if that's still true (I'm reminded of the recent situation surrounding serde_derive). |
It's still true today, you can't ship pre-compiled binaries with Cargo, So the current best way to distribute binaries is to use GitHub Releases (which is what wasm-bindgen does). |
Hi there!
Would it be possible to distribute the
wasm-pack
binary viacargo
, instead of requiring users to runcurl https://rustwasm.github.io/wasm-pack/installer/init.sh -sSf | sh
?It would make keeping track of the installation easier and would automatically provide the binary when
wasm-pack
is added as dependency tocargo.toml
.Rust
bindgen
also distributes viacargo
.The text was updated successfully, but these errors were encountered: