luau-wasm 0.1a0: Roblox’s Luau Runs in Browser via Pyodide

Roblox’s Luau — the typed, performant Lua variant powering millions of Roblox experiences — just got a first-class WebAssembly build published to PyPI. The package luau-wasm 0.1a0 (276 KB wheel, platform tag pyemscripten_2026_0_wasm32) installs directly in Pyodide and runs in any browser. Try it: live demo.

Why This Matters

Pyodide 314.0 (released June 2026) implements PEP 783 — the pyemscripten platform specification that lets package maintainers publish WASM wheels to PyPI just like native Linux/macOS/Windows wheels. Previously, the Pyodide team manually built and hosted 300+ packages. Now the ecosystem opens to anyone with cibuildwheel and a GitHub Actions workflow.

luau-wasm is the proof-of-concept: a non-Python language runtime (Luau) compiled to WASM, packaged as a Python wheel, installable via micropip in the browser.

import micropip
await micropip.install("luau-wasm")
import luau_wasm
print(luau_wasm.execute(r'''
local animals = {"fox", "owl", "frog", "rabbit"}
table.sort(animals, function(a, b) return #a < #b end)
for i, name in animals do print(i .. ". " .. name .. " (" .. #name .. ")") end
'''))

The 28 Packages Already Using pyemscripten_202*_wasm32

Simon Willison queried PyPI’s public BigQuery dataset — here’s the early adopter list (most recent first):

Notable: The majority are Rust crates compiled via wasm32-unknown-emscripten — the pyemscripten platform tag is becoming the de facto standard for Rust-to-Pyodide distribution.

How to Build Your Own pyemscripten Wheel

1. Add cibuildwheel to your GitHub Actions workflow
2. Configure platform: CIBW_PLATFORM="emscripten" (or CIBW_ARCHS_WASM32="wasm32")
3. Set build frontend: Ensure pyproject.toml has [build-system] with requires = ["setuptools", "wheel", "cibuildwheel"]
4. Publish to PyPI — the wheel gets the pyemscripten_2026_0_wasm32 tag automatically

Simon’s luau-wasm repo has a complete, minimal example — including the HTML demo page that loads Pyodide, installs the package, and provides an interactive editor.

What This Unlocks

The Catch (June 2026)

• Pyodide 314.0 required — older versions don’t recognize pyemscripten platform tags
• WASM32 only — no wasm64 support yet
• Binary size matters — 276 KB for luau-wasm is lean; larger crates (arrow, pydantic_core) push 10-50 MB
• Threading / SIMD — limited to what Emscripten + browser exposing; pthreads need COOP/COEP headers

Quick Answers

Can I run this in Node.js / Bun / Deno?
No — luau-wasm targets the Pyodide / Emscripten runtime (WASI-style imports, JS Promise integration). For standalone WASM, compile Luau directly via wasm32-wasi.

Is this “Python in the browser”?
It’s Luau in the browser, distributed via Python packaging tooling. The wheel contains a .wasm binary + Python shim that calls luau_wasm.execute(string).

Why publish a non-Python language as a Python wheel?
Because PyPI + micropip is the most frictionless distribution mechanism for Pyodide. No CDN, no version pinning, no manual fetch — await micropip.install("luau-wasm") just works.

What’s the performance like?
Luau’s JIT is disabled in WASM (no executable memory in browser). Interpreter-only mode — fast enough for scripting, not for heavy compute. See luau.org for native benchmarks.

Source: Simon Willison — “Publishing WASM wheels to PyPI for use with Pyodide” (June 13, 2026); PyPI warehouse PR #19804 (landed April 21, 2026); PEP 783 — PyEmscripten platform.

Live demo: simonw.github.io/luau-wasm/ • Pyodide REPL: pyodide.org/console.html • BigQuery SQL: gist.github.com/simonw/4a34a49fca63bc09c50bc31e17b3d33b

Related: Pyodide 314.0 release notes • How to publish WASM wheels to PyPI • Running Rust in the browser with Pyodide

Quick Answers

Q: Can I run luau-wasm in Node.js / Bun / Deno?

FAQ

Q: Can I run luau-wasm in Node.js / Bun / Deno?
A: No — it targets the Pyodide/Emscripten runtime (WASI-style imports, JS Promise integration). For standalone WASM, compile Luau directly via wasm32-wasi.

Q: Is this “Python in the browser”?
A: It’s Luau in the browser, distributed via Python packaging tooling. The wheel contains a .wasm binary + Python shim calling luau_wasm.execute(string).

Q: Why publish a non-Python language as a Python wheel?
A: Because PyPI + micropip is the most frictionless distribution for Pyodide. No CDN, no version pinning, no manual fetch — await micropip.install("luau-wasm") just works.

Q: What’s the performance like?
A: Luau’s JIT is disabled in WASM (no executable memory in browser). Interpreter-only mode — fast enough for scripting, not heavy compute. See luau.org for native benchmarks.

Q: How do I build my own pyemscripten wheel?
A: Add cibuildwheel to GitHub Actions, set CIBW_PLATFORM="emscripten", configure pyproject.toml build-system, publish to PyPI. Simon’s luau-wasm repo has a minimal working example.

Bottom Line

luau-wasm 0.1a0 proves the PyPI + Pyodide + pyemscripten pipeline works for any language that compiles to WASM. 28 packages (mostly Rust crates) already use it. If you’ve been waiting for a standard way to ship WASM binaries to the browser via pip install, it’s here — and the tooling is cibuildwheel + one GitHub Actions workflow.