Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions Cargo.lock

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion Cargo.toml
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ default = []

[target.'cfg(target_family="wasm")'.dependencies]
getrandom = { version = "0.2", features = ["js"] }
js-sys = "0.3.77"
js-sys = "0.3.91"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dependency version conflict breaks wasm sub-project build

High Severity

Bumping js-sys to 0.3.91 in the root Cargo.toml introduces an irreconcilable dependency conflict with the wasm/ sub-project. js-sys 0.3.91 requires exactly wasm-bindgen = "=0.2.114", but wasm/Cargo.toml pins wasm-bindgen = "=0.2.100". Since wasm/Cargo.toml depends on chialisp via a path dependency, Cargo cannot satisfy both exact-version constraints simultaneously, causing the wasm/ sub-project to fail dependency resolution and be unbuildable.

Fix in Cursor Fix in Web

wasm-bindgen = { version = "^0.2.100", features = ["serde-serialize"] }

[target.'cfg(not(target_family="wasm"))'.dependencies]
Expand Down
Loading