Install wasmer with Homebrew, MacPorts, Nix, pacman, scoop, winget

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• wasmer

Project history

Wasmer reached 1.0 general availability on January 5, 2021. The 1.0 announcement emphasized a stabilized API, much faster compilation, cross-compilation, a headless mode for smaller deployments, and multiple compiler and engine choices.

Secondary coverage of the 1.0 release noted that Wasmer's journey had started more than two years earlier with version 0.1.0 and connected the release to the broader rise of server-side WebAssembly. Wasmer's architecture became recognizable for pluggable compilers and engines, including Singlepass, Cranelift, LLVM, JIT execution, and native-code artifacts.

Wasmer 2.0 followed in 2021 with SIMD, reference types, and performance improvements. Wasmer 3.0 added the ability to create native executables from Wasm for Windows, Linux, and macOS, while Wasmer 4.0 introduced a new runner architecture, stabilized WASIX support, and folded WAPM more directly into the Wasmer product story.

By the mid-2020s Wasmer's public messaging had shifted from just a runtime to a WebAssembly cloud platform. Wasmer 5.0 highlighted additional backend support such as V8, Wasmi, and WAMR for iOS scenarios, and later releases continued to connect the runtime with edge hosting, deploy flows, and sandboxed server workloads.

Adoption history

Wasmer's adoption has two overlapping tracks. One is embedding: language bindings for Python, Go, Ruby, Java, and other ecosystems let applications run Wasm modules through a native library API. Official blog posts around the 1.0-era bindings describe stable APIs, WASI support, and millions of package installations in the Python embedding.

The other track is application distribution. WAPM was created as a WebAssembly package manager and later unified into the Wasmer CLI and website. Wasmer's own WAPM revamp post said community support rose after Wasmer 1.0, 2.0, and 2.1 and that apps, libraries, and smart contracts were using Wasmer in production environments.

Wasmer's later WASIX and Edge work made it especially relevant to developers trying to run POSIX-like programs, websites, and server workloads in a Wasm sandbox. That puts it in a different adoption lane from pure embedders: it competes with containers and serverless platforms as much as with other Wasm engines.

How it is used

CLI users run modules and packages with wasmer run, publish packages through Wasmer-oriented workflows, or create native executables from Wasm artifacts. Embedding users depend on language packages or the Rust crate to compile, instantiate, and call WebAssembly modules from a host application.

Wasmer is often selected when a project wants a broad cross-platform runtime with multiple compiler backends, language bindings, or a Wasm-native package/deploy story. Wasmtime is commonly chosen for Bytecode Alliance standards work and capability security, while WasmEdge is commonly chosen for CNCF and edge/container integration; Wasmer's package-nerd identity is its runtime-plus-registry-plus-edge-platform arc.

Why package nerds care

Wasmer is historically important because it tried to make WebAssembly feel like a universal application format, not just a browser compilation target or an embeddable VM. WAPM and later wasmer.toml workflows gave package managers a concrete example of Wasm modules as named, versioned, runnable artifacts.

It is also a useful case study in runtime packaging complexity. A single Wasmer release can involve Rust crates, language bindings, native binaries, compiler backends, WASI/WASIX behavior, package registry semantics, and edge deployment tooling.

Timeline

• 2018-2019: Wasmer's early 0.x line established the project before the 1.0 release.
• 2021-01-05: Wasmer 1.0 became generally available with a stabilized API and major performance work.
• 2021: Wasmer 2.0 added SIMD, reference types, and runtime performance improvements.
• 2022: Wasmer 3.0 added native executable generation from Wasm.
• 2023: Wasmer 4.0 introduced the runner architecture, stabilized WASIX, and unified WAPM into Wasmer.
• 2024: Wasmer 5.0 highlighted additional backend support and broader platform reach.
• 2026: Wasmer 7.0 added an experimental async API, exception support in Cranelift, RISC-V and multi-value support in Singlepass, and fuller dynamic linking support in WASIX.

Related projects

• Wasmtime is a closely related WebAssembly runtime, especially for WASI and component-model standards work.
• WasmEdge is a related runtime with stronger CNCF and cloud-native edge positioning.
• Cranelift, LLVM, Singlepass, V8, Wasmi, and WAMR appear in Wasmer's compiler/backend story.
• WAPM and WASIX are central related projects in Wasmer's package and POSIX-like application ecosystem.

Sources

• https://blog.wasmer.io/wasmer-1-0-3f86ca18c043
• https://github.com/wasmerio/wasmer
• https://wasmer.io/posts/announcing-wasmer-3_0
• https://wasmer.io/posts/introducing-wasmer-v5
• https://wasmer.io/posts/wapm-revamp
• https://wasmer.io/posts/wasmer-2_0
• https://wasmer.io/posts/wasmer-4_0
• https://wasmer.io/posts/wasmer-7
• https://wasmer.io/posts/welcome-to-the-new-wasmer
• https://www.infoq.com/news/2021/01/wasmer-generally-available/