You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Gate the server side behind a default server feature #18
The crate has no Cargo features, so a wasm guest that wants only the messages and the request/response/resource helpers cannot depend on it: tokio (rt-multi-thread, signal) and aws-lc-sys do not build for wasm32-wasip3.
A server feature, on by default, gating server.rs, metrics.rs, logging.rs, the server-side Error variants, the generated tonic client/server and FILE_DESCRIPTOR_SET keeps every current dependent as is, and with default-features = false the rest compiles for wasm (prototyped against function-wasm's rust scaffold: it builds, passes the guest suite and drops the vendored proto and protoc).
Closing without a change: the default server feature (#19) turned out more invasive than the one consumer's gain. function-wasm keeps vendoring the proto for its WebAssembly guests.
Activity
feat: gate the server behind a default feature
jonasz-lasut commentedon Oct 7, 2026
Closing without a change: the default server feature (#19) turned out more invasive than the one consumer's gain. function-wasm keeps vendoring the proto for its WebAssembly guests.