Installer wazero avec Homebrew, apk, Nix, zypper, winget

Liens du projet

• Page d'accueil
• Dépôt

Commandes et alias

• wazero

Historique du projet

The project history page says wazero began as Takeshi Yoneda's hobby project in mid 2020 and was sponsored by Tetrate as a top-level project in late 2021. The original motivation was to let Go programs embed WebAssembly host environments without relying on CGO-backed runtimes such as V8, Wasmtime, Wasmer, or WAVM.

The official site says wazero 1.0 was released in March 2023. By that point, the project had positioned itself as both an embeddable Go library and a standalone CLI, with WebAssembly Core Specification compliance and a focus on cross-compilation-friendly deployment.

The project later moved under the `wazero/wazero` GitHub organization while retaining Tetrate stewardship and branding in docs and package metadata. Release notes through the 1.x series document work on WASI support, compiler performance, Go version compatibility, experimental proposals, and security-oriented execution details.

Historique d'adoption

wazero adoption tracks the rise of server-side and embedded WebAssembly in Go systems. The project history names plugin systems, proxy extension through Proxy-Wasm, server-side rendering, and Open Policy Agent-style policy/plugin use as motivating examples.

The official homepage says the 1.0 release is used by many projects and production sites. Package metadata in this batch also shows distribution through Homebrew, Alpine, Nix, winget, and openSUSE, reflecting use both as a developer CLI and as a runtime dependency in Go-based tooling.

Modes d'utilisation

Library users import wazero to run WebAssembly modules inside Go programs, define host functions, wire WASI, and let users write plugins in languages that compile to Wasm, including AssemblyScript, C, C++, Rust, Zig, Go, and TinyGo.

CLI users run Wasm modules directly for testing, scripting, or packaging workflows. The zero-CGO design is especially useful for static binaries, cross-compilation, container images, and environments where adding a native Wasm runtime library would complicate builds or distribution.

Pourquoi les passionnés de paquets s'y intéressent

wazero matters to package nerds because it changes the dependency tradeoff for WebAssembly in Go: a package can embed a runtime without dragging in a C ABI, libc assumptions, or platform-specific shared libraries. That makes it attractive for Homebrew formulae, distro packages, and small containers that prefer boring Go binaries.

Its significance is also cultural. It belongs to the wave of Wasm-as-a-plugin-runtime tools, but it speaks fluent Go packaging: module import, no CGO, cross-compilation, and API integration rather than a separate server.

Chronologie

• 2020: wazero begins as Takeshi Yoneda's hobby project.
• 2021: Tetrate sponsors wazero as a top-level project.
• 2023-03: wazero 1.0 is released.
• 2024: 1.x releases continue with compiler, WASI, and Go-version support work.
• 2025-2026: The project continues under the wazero GitHub organization with Tetrate branding and stewardship.

Related projects

• wazero is related to WebAssembly, WASI, Proxy-Wasm, TinyGo, Open Policy Agent, Wasmtime, Wasmer, V8, WAVM, and the older Go wasm runtime wagon that the wazero history page mentions.

Sources

• https://github.com/wazero/wazero
• https://github.com/wazero/wazero/releases
• https://wazero.io/
• https://wazero.io/community/history/
• https://wazero.io/docs/