Loosen wasm-bindgen restrictions; specify split-linked-modules = true

To (hopefully) workaround the previous reason for the pinning: wasm-bindgen no longer emitting snippets, causing wasm-bindgen-rayon to break.
grafana · Dec 12, 2024 · 275daa1 · 275daa1
1 parent e6ed15f
commit 275daa1
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/Cargo.toml b/Cargo.toml
@@ -62,7 +62,7 @@ tinyvec = "1.6.0"
 tracing = "0.1.40"
 tracing-subscriber = { version = "0.3.18", default-features = false }
 tsify-next = { version = "0.5.3", default-features = false, features = ["js"] }
-wasm-bindgen = "=0.2.99"
+wasm-bindgen = "0.2.99"
 
 assert_approx_eq = "1.1.0"
 criterion = "0.5.1"

diff --git a/js/augurs-dtw-js/Cargo.toml b/js/augurs-dtw-js/Cargo.toml
@@ -37,6 +37,8 @@ wasm-bindgen-rayon = { version = "1.2.1", optional = true }
 [package.metadata.wasm-pack.profile.release]
 # previously had just ['-O4']
 wasm-opt = ['-O4', '--enable-bulk-memory', '--enable-threads']
+# See https://github.com/RReverser/wasm-bindgen-rayon/issues/16.
+split-linked-modules = true
 
 [lints]
 workspace = true