Is your feature request related to a problem? Please describe.
Including additional client-side renderer examples in the docs would give a greater wealth of modular options as far as renderers go, since you're free to drop in whatever you want to this stage of the pipeline.
Describe the solution you'd like
FFmpeg.wasm packages a bunch of options for output animations/video able to be rendered in the browser client-side, or on a Node server. It can render a frame buffer as gifs, WebM, WebP, mp4/H.264, H.256, etc, and supports multi-threading for mp4 rendering. The library also supports audio encoding which may come in handy for the future plans of building in an audio pipeline.
Adding an example using FFmpeg.wasm to the docs would be awesome! Probably no need to bundle the renderer directly in urpflanze since it's quite modular by design. This could be another solid alternative to using the raw zip export or mattdesl/mp4-h264.