So I am able to create both a raw wasm and a wasm component from the fastly.wit, but I just get unresolved imports when I try and serve it…
It feels like I am missing one layer or setting an abi version somewhere which would let me leverage the fastly.wit?
compute-at-edge.witx describes the wasm ABI available on compute@edge. The
We can’t yet make any promises on when components & wit interfaces are available on compute@edge, but a bunch of us are working hard on it, so stay tuned!
Thanks for the reply - I would be v. interested in looking at / reusing the thunking code you mentioned, is it tucked away in one of the online projects?
it is split between the
https://github.com/fastly/js-compute-runtime/tree/main/runtime/js-compute-runtime/host_interface directories, where the latter is a more c++ish abstraction over the api presented by the wit-bindgen generated c api