Skip to content

Gate the server side behind a default server feature #18

Closed

Description

@jonasz-lasut

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).

Activity

  1. added a commit that references this issue on Oct 7, 2026
    2e156fb
  2. jonasz-lasut commented on Oct 7, 2026

    @jonasz-lasut
    CollaboratorAuthor

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions