The current discussion on the cranelift merge reminded me: I find it confusing that the primary interface to wasmtime is the crate called "wasmtime" but it lives in "crates/api" for historical reasons.
Could we rename it to crates/wasmtime?
I suggested this a while ago and the argument for the current scheme is that you can run cargo run -- ... to build and run the wasmtime cli or cargo install --path . to build and install a local version of wasmtime, which seemed like a useful thing for developers to be able to do.
I'm not totally convinced, but this is also not something I care enough about to raise a stink either way
I'm not talking about the top-level crate being wasmtime-cli.
I'm talking about the directory name crates/api.
I don't recall a reason why we use crates/api, other than that it used to be called wasmtime-api.
Renaming it to crates/wasmtime sounds reasonable to me.
Last updated: Dec 06 2025 at 06:05 UTC