Victor Adossi
Victor Adossi
Just a note, but if you build a WebAssembly module versus a WebAssembly component you can tell the difference between them (standard tooling like `file` already supports this): ``` ➜...
Ah thanks for re-iterating what you wrote -- I think what I missed was: > it is basically now just a second bytecode wasm supports > ... > I think...
Just to clarify for anyone trying to reproduce, with `wstd` cloned you can run: ```console cargo component build --release --example http_client --target wasm32-wasip2 ``` I've removed the static function machinery...
An update here to mirror the PR -- the member access issues are one thing, but the deeper issue looks to be currently incomplete trailer support Jco -- we'll have...
Hey @brooksmtownsend so the binaries for a local provider are actually cached (the EXEs)... I think this might not be as easy as it seems. A few things: - Didn't...
> I think that we do have that option, and it makes sense for OCI, but I don't really see the case where we'd want to cache the binary when...
Thanks for the detailed writeup @thomas9911 !
Hey @ctaggart what do you think about the following: - `types/wit` - `types/jco/wit` - `types/jco/generated` Do any of those feel intuitive to you? All three of the axes here *feel*...
For those that might pick up this issue, note that a reasonable solution seems to be: - Make the `--wit` argument optional (and use the `wit` folder if it exists)...
This was resolved by https://github.com/bytecodealliance/ComponentizeJS/pull/207