-
Notifications
You must be signed in to change notification settings - Fork 258
New issue
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
WASI Preview 2 support #2289
Comments
unfortunately, until WASI v1.0, I would recommend to use wasip1 because of the confusion and drama around WASI. See #2200 as well where we clearly state that we will never support Component Model as well until it lands W3C recommendation 😉 |
ps I have never encountered a single person with a solid real world application who could elaborate on why they need them (esp. component model) and why the current WASI p1 doesn't fit for them. anyway nuff said, thank you for opening the issue as it's good to clarify our position publicly |
thanks for the quick response and clarifying that! You could look at ConduitIO/conduit#1646 if curious for a real world use case - in particular this discussion for how to embed Benthos in a Conduit pipeline. |
i don't see any reason why it cannot be done without wasip2/component model. I am 99.99999% sure you won't need them |
Is your feature request related to a problem? Please describe.
A recent announcement for using TinyGo with wasi preview 2 opened up a lot of possibilities. However, it can only work with a runtime that supports wasip2.
Describe the solution you'd like
A clear and concise description of what you want to happen.
It would be great if wazero could add support for wasip2
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: