Deno currently offers partial support for WASI through the wasicap_snapshot_preview1 interface. This partial support limits the ability to run a wide range of WASI modules that are designed for modern environments. The lack of compatibility with the evolving WASI 0.2 standard prevents users from leveraging the enhanced security features, broader module compatibility, and cutting-edge development capabilities that WASI 0.2 provides. This limitation affects both Deno and Deno Deploy users, restricting their ability to fully utilize WebAssembly for various production use cases.
I have an issue when trying to run modern WASI modules on Deno and Deno Deploy, as they do not fully support the WASI 0.2 standard. This limits module compatibility, security, and performance, making it difficult to develop and deploy WebAssembly applications effectively.
Describe the solution you'd like
I would like Deno to implement full support for the WASI 0.2 standard. This would involve updating the current WASI interface to be compatible with WASI 0.2, enabling the execution of a wider range of WASI modules with enhanced security features and improved performance.
Describe alternatives you've considered
One alternative considered was to continue using the existing wasicap_snapshot_preview1 interface, but this approach does not address the compatibility issues with newer WASI modules or the benefits offered by WASI 0.2. Another alternative was to explore third-party tools or libraries to bridge the gap, but this adds complexity and does not provide a native solution within Deno and Deno Deploy.
Documentation, Adoption, Migration Strategy
Documentation:
Comprehensive documentation should be provided to guide users on how to use the new WASI 0.2 support within Deno and Deno Deploy.
Examples and use cases demonstrating the benefits and capabilities of WASI 0.2 should be included.
Migration guides to help users transition from wasicap_snapshot_preview1 to WASI 0.2.
Adoption:
Clear communication about the new feature through Deno's release notes, blog posts, and community channels.
Encourage early adopters to provide feedback and share their experiences to refine the implementation.
Migration Strategy:
Ensure backward compatibility where possible to allow gradual migration.
Provide tools or scripts to assist in updating existing WASI modules to be compatible with WASI 0.2.
Host webinars or workshops to help users understand and adopt the new features.
What problem are you trying to solve?
Deno currently offers partial support for WASI through the
wasicap_snapshot_preview1interface. This partial support limits the ability to run a wide range of WASI modules that are designed for modern environments. The lack of compatibility with the evolving WASI 0.2 standard prevents users from leveraging the enhanced security features, broader module compatibility, and cutting-edge development capabilities that WASI 0.2 provides. This limitation affects both Deno and Deno Deploy users, restricting their ability to fully utilize WebAssembly for various production use cases.I have an issue when trying to run modern WASI modules on Deno and Deno Deploy, as they do not fully support the WASI 0.2 standard. This limits module compatibility, security, and performance, making it difficult to develop and deploy WebAssembly applications effectively.
Describe the solution you'd like
I would like Deno to implement full support for the WASI 0.2 standard. This would involve updating the current WASI interface to be compatible with WASI 0.2, enabling the execution of a wider range of WASI modules with enhanced security features and improved performance.
Describe alternatives you've considered
One alternative considered was to continue using the existing
wasicap_snapshot_preview1interface, but this approach does not address the compatibility issues with newer WASI modules or the benefits offered by WASI 0.2. Another alternative was to explore third-party tools or libraries to bridge the gap, but this adds complexity and does not provide a native solution within Deno and Deno Deploy.Documentation, Adoption, Migration Strategy
Documentation:
wasicap_snapshot_preview1to WASI 0.2.Adoption:
Migration Strategy: