wasm-bindgen crate versioning

[rsmolcic-3mi]

Hello guys,

maybe a newbie question, but is there a specific reason that under the dependencies for the v11.5 the wasm-bindgen crate is explicitly set to 0.2.87?

I'm currently facing an issue where I'm using the flutter_rust_bridge which requires wasm-bindgen ^0.2.92, but the cardano-serialization-lib explicitly requires the 0.2.87 version, giving me problems considering no version for wasm-bindgen can resolve the conflict.

error: failed to select a version for wasm-bindgen. ... required by package flutter_rust_bridge v2.1.0... which satisfies dependencyflutter_rust_bridge = "=2.1.0"of packagerust_lib_kratos v0.1.0 (/my/path/Projects/Flutter/kratos/rust)versions that meet the requirements^0.2.92` are: 0.2.92

all possible versions conflict with previously selected packages.

previously selected package wasm-bindgen v0.2.87
... which satisfies dependency wasm-bindgen = "=0.2.87" of package cardano-serialization-lib v11.5.0
... which satisfies dependency cardano-serialization-lib = "=11.5.0" of package rust_lib_kratos v0.1.0 (/my/path/Projects/Flutter/kratos/rust)

failed to select a version for wasm-bindgen which could resolve this conflict`

Any ideas how to tackle this?

[rsmolcic-3mi]

The upper comment seems to be a bot (@HubDevi), in case someone visits this topic beware of the link.

[lisicky]

Hi @rsmolcic-3mi ! You can override dependency in toml file to specify wasm bindgen version or also the latest CSL 12 beta has updated wasm bindgen dependency

[rsmolcic-3mi]

Hey @lisicky, I’ve tried the latest beta but it also has an unsupported mismatch. The latest beta uses 0.2.90 explicitly, and the flutter_rust_bridge requires 0.2.92 and above.

[lisicky]

@rsmolcic-3mi we will bump bindgen version in the next beta if we won't have any issues with moving to 0.2.92. But anyway we can't add compatibility with all rust packages and I suggest to override dependency, see here and here

[rsmolcic-3mi]

Thank you @lisicky, will have to keep track of the versions manually, but at least I've got it working :)