wasm-compatibility

To check WASM compatibility for a marimo notebook, provide its file path. The skill analyzes imports and PEP 723 dependencies, validates them against Pyodide packages, and flags incompatible patterns blocking browser execution.

Your marimo notebook fails in the browser playground because non-pure-Python dependencies or native extensions are incompatible with WASM. The skill identifies these blockers by comparing imports against Pyodide's package list.

Pyodide does not support all Python packages in WASM environments. The skill validates marimo notebook dependencies against Pyodide's built-in package list and flags native extensions that cannot execute in browser runtimes.

To validate dependencies for WebAssembly execution, the skill extracts packages from the PEP 723 metadata block and import statements, mapping imports to PyPI distributions and checking them against Pyodide compatibility.

Common WASM compatibility issues in marimo notebooks include native extension dependencies and incompatible import patterns. The skill detects these by analyzing dependencies and validating against Pyodide's supported package list.

Native Python extensions cannot be used in a marimo WASM environment because they fail to execute in browser runtimes. The skill flags these non-pure-Python dependencies during the compatibility check.