We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There are three different types of component adapters, currently we only handle reactor and command and need to support proxy:
https://github.com/bytecodealliance/wit-bindgen/tree/main?tab=readme-ov-file#creating-components-wasi
wasi_snapshot_preview1.command.wasm - use this for CLI applications. wasi_snapshot_preview1.reactor.wasm - use this for applications that don't have a main function for example: for example a process that responds to an event. wasi_snapshot_preview1.proxy.wasm - use this for applications fed into wasmtime serve for example.
The text was updated successfully, but these errors were encountered:
This will no longer be an issue after dotnet/runtimelab#2614 merges. wasm-component-ld (which ships as part of WASI-SDK) will manage this
Sorry, something went wrong.
closing in favor of #26
No branches or pull requests
There are three different types of component adapters, currently we only handle reactor and command and need to support proxy:
https://github.com/bytecodealliance/wit-bindgen/tree/main?tab=readme-ov-file#creating-components-wasi
The text was updated successfully, but these errors were encountered: