wasm-compatibility
Verify marimo notebook compatibility with WebAssembly environments and identify incompatible dependencies or code patterns.
- Analyzes both PEP 723 metadata and import statements to extract all notebook dependencies, then cross-references against Pyodide's built-in packages and pure-Python availability
- Detects incompatible packages with native C/Rust extensions (torch, tensorflow, psycopg2, etc.) and suggests WASM-friendly alternatives
- Scans code for WASM-blocking patterns including subprocess calls, multiprocessing, hard-coded file paths, sqlite3, and environment variable access
- Generates a detailed report with package compatibility status, code issues by cell location, and concrete remediation steps for failing notebooks
WASM Compatibility Checker for marimo Notebooks
Check whether a marimo notebook can run in a WebAssembly (WASM) environment — the marimo playground, community cloud, or exported WASM HTML.
Instructions
1. Read the notebook
Read the target notebook file. If the user doesn't specify one, ask which notebook to check.
2. Extract dependencies
Collect every package the notebook depends on from both sources:
More from marimo-team/skills
marimo-notebook
Write a marimo notebook in a Python file in the right format.
2.5Kmarimo-batch
An opintionated skill to prepare a marimo notebook to make it ready for a scheduled run.
1.6Kanywidget-generator
Generate anywidget components for marimo notebooks.
1.4Kjupyter-to-marimo
Convert a Jupyter notebook (.ipynb) to a marimo notebook (.py).
1.3Kimplement-paper
Implement a research paper as an interactive marimo notebook together with the user. Start by understanding what the user wants to explore, fetch the paper via alphaxiv, then build a focused notebook.
881add-molab-badge
Add "Open in molab" badge(s) linking to marimo notebooks. Works with READMEs, docs, websites, or any markdown/HTML target.
765