Export WASM to folder for self-publishing on personal web site

[astrowonk]

marimo.app is very cool and I was excited to see the WASM support. But, WASM apps should be able to just be turned into a folder than can deployed on any web server (nginx, apache, etc.) Shiny Live for example has an easy shinylive export myapp site command that turns the app into a folder I can upload to my nginx server.

Whereas for now, wasm notebooks seem to require using marimo.app. Is there a plan to have an export option someday? Thanks!

[akshayka]

This is a great idea, and has been requested a few times. We very well may do this in the future.

In the meantime, can you get by with iframing marimo.app (https://docs.marimo.io/guides/wasm.html#embedding)?

[astrowonk]

Hmm, I don't think so. I keep most of my complex code in separate python files, that I import into the Marimo notebook to use/visualize. These functions/classes are not defined in the notebook itself. Similarly at some point I'd want to read data from a local file, assuming that works.

[dmadisetti]

@astrowonk Support for external files would require some work to the wasm virtual file system. But a "caching" system is being considered, that could run code on export, but then save the computed value to just be loaded in the export. This would also be faster to the end user

[jettil]

That would be a nice feature! I Think it would solve many data security concerns and help publish marimo notebooks to non tech colleagues

[aszenz]

Lot of private data sources cannot be loaded from cross origin, so embedding an iframe isn't useful.

Starboard notebook allows easy embedding into any webpage using a plain js+css file: https://github.com/gzuidhof/starboard-notebook

[akshayka]

@aszenz , @jettil , and @astrowonk : we now have the pieces to make this possible, with marimo islands. In fact this is possible today using islands yourself, but I recognize that's more cognitive overhead than a CLI command. We'll add support for this.

[akshayka]

Issue: #1882

[aszenz]

@aszenz , @jettil , and @astrowonk : we now have the pieces to make this possible, with marimo islands. In fact this is possible today using islands yourself, but I recognize that's more cognitive overhead than a CLI command. We'll add support for this.

Is it possible to have the notebook editor in the islands, I thought it's only meant for rendering the content

[dmadisetti]

@aszenz Islands allows you to have editable cells- but yes it is more of an export than a notebook experience. The cells are still reactive and powered by wasm- but you can't create or delete cells as is.

You could hack up a solution particular to your islands integration if you wanted to make it more "notebook" like, but I think it'd just add additional surface area for core marimo - especially since the notebook experience is so well integrated.

[colluca]

@aszenz , @jettil , and @astrowonk : we now have the pieces to make this possible, with marimo islands. In fact this is possible today using islands yourself, but I recognize that's more cognitive overhead than a CLI command. We'll add support for this.

This still doesn't allow "storing code in separate python files" as @astrowonk mentioned, is that correct? I found myself in a similar need when experimenting with WASM notebooks.

[mscolnick]

Good news! This is now possible in marimo 0.10.0, here are the docs. (related PR).

# export as readonly, with code locked
marimo export html-wasm notebook.py -o output_dir --mode run
# export as an editable notebook
marimo export html-wasm notebook.py -o output_dir --mode edit

The exported HTML file will run your notebook using WebAssembly, making it completely self-contained and executable in the browser. This means users can interact with your notebook without needing Python or marimo installed.

Options:

• --mode: Choose between run (read-only) or edit (allows editing)
• --output: Directory to save the HTML and required assets