(feat) Bring your own UDP socket and WASM compilation target

[guest271314]

I've been trying to builda WebTransport server in the browser for a while now. The idea is to use Direct Sockets UDPSocket, compile a WebTranport library to WASM or JavaScript that uses only Web API's.

Ideally everything should work the same. The TLS/QUIC/WebTransport libraries just get passed data from UdpSocket readable (Uint8Array) and get back the raw data to evaluate in JavaScript. Then JavaScript can pass data back to the WASM/JavaScript implementation and get back a TLS/QUIC/WebTransport packet to write to UDPSocket.

What I've tried so far:

fails-components/webtransport#354
https://github.com/guest271314/quinn-wasm/tree/direct-sockets
toyobayashi/emnapi#178

Related: vmeansdev/webtransport-bun#12

[guest271314]

@endel How do I create an object file of the wasm build target with build-obj?

[endel]

Hi @guest271314, I've just added a new step for you in the wasm-experiment branch, so you can run:

zig build wasm-obj

This will now output zig-out/wasm/quic.o 🙌

[guest271314]

WTH?

error: Your local changes to the following files would be overwritten by merge:
build.zig
Please commit your changes or stash them before you merge.

[guest271314]

Figured it out, git stash.