wasm-compatibility

To check marimo notebook WebAssembly compatibility, analyze notebook dependencies from PEP 723 metadata and imports for Pyodide support, then scan for unsupported code patterns like subprocess usage. This produces a PASS, WARN, or FAIL remediation report for WASM environments.

Python notebooks fail in Pyodide environments due to incompatible dependencies unavailable in WebAssembly or unsupported runtime patterns like multiprocessing, subprocess calls, and filesystem assumptions. Detecting these browser limitations and package issues before deployment resolves the failures.

Unsupported code patterns when exporting marimo notebooks to WASM include subprocess usage, filesystem assumptions, multiprocessing, debugger calls, and unavailable environment access. Scanning for these patterns ensures Python notebooks run correctly in Pyodide and browser playgrounds.

Pyodide does not support all Python packages used in marimo playgrounds. Dependency compatibility analysis extracts package requirements from PEP 723 metadata and imports, then checks each package against Pyodide and WebAssembly constraints to identify unsupported libraries.

Validate dependencies for marimo cloud deployment by extracting package imports and PEP 723 metadata from the notebook, then verifying each dependency against Pyodide and WebAssembly compatibility lists. This generates actionable package status assessments for cloud notebooks.

Running Python notebooks in WebAssembly environments has limitations including unavailable native subprocess calls, restricted filesystem access, unsupported multiprocessing, and missing environment variables. Scanning code for these patterns prevents runtime failures in Pyodide and WASM exports.