Schema Version Mismatch Error when Using cargo leptos watch
in WSL Ubuntu Environment
#3908
Unanswered
MachoMaheen
asked this question in
Q&A
Replies: 1 comment
-
I'm assuming that updating the While compiling you should see which version is being compiled, you can also look into your |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the Bug
When using
cargo leptos watch
command on a Rust project targeting wasm32-unknown-unknown in a WSL Ubuntu environment, a schema version mismatch error occurs between cargo-leptos and wasm-bindgen.Steps to Reproduce
cargo leptos watch
command on a Rust project targeting wasm32-unknown-unknown.Expected Behavior
I expected
cargo leptos watch
to compile the project successfully without any schema version mismatch errors.Actual Behavior
The
cargo leptos watch
command fails with the following error message:Error: at /home/macho/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-leptos-0.2.16/src/compile/front.rs:47:30
Caused by:
0: at /home/macho/.cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-leptos-0.2.16/src/compile/front.rs:122:10
1:
Additionally, the error message suggests trying to update the wasm-bindgen dependency or the wasm-bindgen-cli binary, both of which have been attempted without success.
Additional Context
cargo leptos watch
command on a project targeting wasm32-unknown-unknown.This issue is hindering further development progress, and any assistance or guidance in resolving it would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions