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
Describe the bug
Without an update of the wasm-bindgen dependency from v0.2.13 to v0.2.17 the initial npm run build-debug on the chapter-zero branch fails to compile.
Expected behavior npm run build-debug compiles without error.
Screenshots
Additional context
It's no trouble to run cargo update -p wasm-bindgen, but I think that slows readers down. Luckily the error messages are very clear, but it might still be intimidating to a newcomer to troubleshoot this.
For what it's worth, I'm using
nvm - v0.33.11
Node.js - v10.9.0
npm - v6.4.0
cargo - 1.29.0-nightly (6a7672ef5 2018-08-14)
wasm-bindgen-cli - v0.2.17
The text was updated successfully, but these errors were encountered:
reillysiemens
changed the title
wasm-bindgen dependency in Cargo.toml is out of date
wasm-bindgen dependency in Cargo.toml is out of date in chapter-zero
Aug 22, 2018
Hey @reillysiemens to avoid this we should put 0.2 as the dep for wasm-bindgen in the Cargo.toml that way it always uses the newest version and not include a Cargo.lock. Can you confirm this works for the code as is today?
Since Cargo.toml in the master branch specifies the wasm-bindgen dependency to be 0.2,
this issue is resolved in the master branch and can now be closed 👍
The project still builds and runs successfully as of today (04/29/2020)
Describe the bug
Without an update of the wasm-bindgen dependency from v0.2.13 to v0.2.17 the initial
npm run build-debug
on thechapter-zero
branch fails to compile.To Reproduce
Steps to reproduce the behavior:
git clone https://github.com/rustwasm/wasm_game_of_life.git
cd wasm_game_of_life
git checkout -b chapter-zero origin/chapter-zero
npm install
npm run build-debug
Expected behavior
npm run build-debug
compiles without error.Screenshots
Additional context
It's no trouble to run
cargo update -p wasm-bindgen
, but I think that slows readers down. Luckily the error messages are very clear, but it might still be intimidating to a newcomer to troubleshoot this.For what it's worth, I'm using
The text was updated successfully, but these errors were encountered: