Yordis Prieto (Apr 12 2026 at 17:16): Yordis Prieto (Apr 12 2026 at 17:16):I traced the issue to the official Google Rust protobuf runtime. The WASM build breaks in the upb layer for wasm32-wasip2, so this looks like missing upstream support more than a local bug.
Maybe we should collaborate with the Google protobuf folks and help push proper direct WASM support there.
Yordis Prieto (Apr 12 2026 at 17:17):@Bailey Hayes I would, if I had any connections :sweat_smile: I feel making protobuffer to work out the getgo will open a lot of doors for adoptions
andreaTP (Apr 13 2026 at 10:23):We started from wasilibs: https://github.com/wasilibs and now we have this: https://github.com/roastedroot/protobuf4j , regardless of the runtime, the wasm build should be a good starting point, we are both patching on top,
The biggest challenge with protoc is "subprocess" support, happy to help when someone want to champion the upstream support!
Bailey Hayes (Apr 13 2026 at 15:54):I started upstream in Abseil aiming to contribute wasip2 target support there. That one has stalled out. https://github.com/abseil/abseil-cpp/pull/1976
guest271314 (Apr 19 2026 at 14:49):I feel making protobuffer to work out the getgo will open a lot of doors for adoptions
I got stuck on the protobuf stuff tryingto compile fails-components/webtransport (depends on Google/quiche which depends on Google/protobuf) to WASM.
There's this https://github.com/aperturerobotics/go-protoc-wasi which I have not tried...
Last updated: May 03 2026 at 22:13 UTC