Skip to content
This repository was archived by the owner on Jan 24, 2024. It is now read-only.
/ wazerox Public archive

wazerox: wazero extended with bleeding-edge features

License

Notifications You must be signed in to change notification settings

wasilibs/wazerox

Folders and files

NameName
Last commit message
Last commit date

Latest commit

4923be6 · Jan 24, 2024
Dec 18, 2023
May 11, 2022
Dec 18, 2023
Dec 18, 2023
Nov 17, 2023
Dec 18, 2023
Dec 18, 2023
Jan 5, 2024
Apr 22, 2023
Dec 18, 2023
Nov 17, 2023
Jan 25, 2023
Feb 14, 2022
May 10, 2022
Mar 1, 2023
May 11, 2022
May 1, 2023
Apr 28, 2023
Jan 5, 2024
Apr 28, 2023
Aug 9, 2023
Jan 24, 2024
Nov 17, 2023
Nov 17, 2023
Nov 17, 2023
Nov 17, 2023
Nov 17, 2023
Jun 1, 2022
Dec 18, 2023
Nov 17, 2023
Jul 1, 2022
Nov 17, 2023
Jul 1, 2022
Nov 17, 2023
Nov 17, 2023
Nov 17, 2023
Nov 17, 2023
Nov 17, 2023
Nov 17, 2023
Apr 15, 2022
Jul 11, 2023
Nov 17, 2023
Nov 17, 2023

Repository files navigation

This repository is inactive. All features have been merged upstream. It may return in the future if needing to experiment again, but there is no expectation or plan for this.

wazerox: wazero extended with bleeding-edge features and likely bugs

WebAssembly Core Specification Test Go Reference License

wazero is a wonderful WebAssembly runtime for Go developers with a priority on stability. This often means it can take time to add new incubating WebAssembly features or completely non-standard ones - there is only so much a project can take on.

wazerox is a fork with a priority on running code for the wasilibs organization. The reality is much existing code out there requires features that are not supported by current WebAssembly or WASI specifications. wazerox allows wasilibs to continue to provide wrappers with zero usage of cgo.

The additions to wazero should be considered mostly be an implementation detail of wasilibs libraries. If you have code that requires these extensions to execute, it is OK to try wazerox, but do expect bugs and best-effort or non-existing support. It is never a good idea to try this library before trying wazero and see if it supports your binary, if it does, use wazero.

Current extensions include:

For further details on the runtime, read about wazero.