tokio mutex avail on wasm

zakstucke · Aug 13, 2024 · 67948d3 · 67948d3
1 parent 59a7138
commit 67948d3
Show file tree

Hide file tree

Showing 2 changed files with 11 additions and 2 deletions.
diff --git a/.zetch.lock b/.zetch.lock
diff --git a/rust/Cargo.toml b/rust/Cargo.toml
@@ -119,6 +119,16 @@ rayon = { version = "1", optional = true }
 # FEAT: cookies:
 wasm-cookies = { version = "0.2", optional = true }
 
+# These features are included in all builds, need tokio sync feature for mutex, which is fine on wasm.
+# Wasm supported features: https://docs.rs/tokio/latest/tokio/#wasm-support
+[dependencies.tokio]
+version = "1"
+features = ["sync"]
+# These are included on top of above features when not wasm:
+[target.'cfg(not(target_arch = "wasm32"))'.dependencies.tokio]
+version = "1"
+features = ["time", "fs", "process", "rt", "io-util"]
+
 [target.'cfg(target_arch = "wasm32")'.dependencies]
 tracing-subscriber-wasm = "0.1.0"
 gloo-timers = { version = "0.3", features = ["futures"] }
@@ -127,7 +137,6 @@ gloo-timers = { version = "0.3", features = ["futures"] }
 # This includes threading (non-blocking stuff that can't be used in wasm)
 tracing-appender = '0.2'
 hostname = "0.3.1"
-tokio = { version = '1', features = ["time", "sync", "fs", "process", "rt", "io-util"] }
 named-lock = "0.4"
 
 [dev-dependencies]