-
-
Notifications
You must be signed in to change notification settings - Fork 83
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
wasm-bindgen version conflict... #176
Comments
Are you using |
Yes. |
In this case you're stuck at version |
I see there is a pull request, is something blocking it getting merged in? My only problem is the version conflict but it makes me nervous because it affects everything in a workspace. web-sys and js-sys also need to be kept at the older version. |
This is an unfortunate reality at the moment with the whole web-sys ecosystem. It's still very unstable and has sometimes breaking changes even on patch version increases so it's necessary to pin the versions down. It's not so bad though because this is "just" a binding for the actual browser JavaScript APIs which are what they are in any case. I'll release an updated version as soon as cargo-leptos updates. |
In my case the problem was fixed simply by deleting Cargo.lock and running cargo check again. |
Leptos unpinned |
Does it not work with the latest wasm-bindgen (0.2.95) ??
cargo metadata
exited with an error: Updating crates.io indexerror: failed to select a version for
wasm-bindgen
.... required by package
leptos-use v0.13.5
... which satisfies dependency
leptos-use = "^0.13.5"
of package...
versions that meet the requirements
=0.2.93
are: 0.2.93The text was updated successfully, but these errors were encountered: