wasm-compatibility

Checking marimo notebook WASM compatibility involves scanning import statements and PEP 723 dependency blocks against Pyodide built-ins. The validation flags non-pure-Python packages and missing metadata to surface incompatibilities before attempting web-based execution.

Pyodide does not support all Python packages in WebAssembly. WASM compatibility checks evaluate dependencies against Pyodide built-ins and flag non-pure-Python packages that require C extensions or system-level access, which cannot run client-side.

Validate marimo notebook dependencies for Pyodide by extracting imports from PEP 723 style script blocks and mapping them to WASM compatibility. This generates a structured report listing incompatible packages and suggested workarounds for client-side execution.

A marimo notebook fails in a WebAssembly environment when it imports non-pure-Python packages unsupported by Pyodide. Scanning for incompatible dependencies, missing SKILL.md metadata, and unsafe runtime patterns identifies the specific blockers preventing WASM execution.

Common limitations when running marimo notebooks in WASM include dependencies on non-pure-Python packages, missing required SKILL.md frontmatter, and runtime code patterns requiring server-side computation. These constraints prevent seamless client-side execution in Pyodide.

Running a marimo notebook with C extensions in Pyodide is generally not possible unless the package is specifically built for WebAssembly. WASM compatibility checks flag these non-pure-Python dependencies and provide remediation steps or suggested workarounds.