penpot/render-wasm
alonso.torres 6bdb5565d8 🐛 Size a WASM grid track by a fill grid child's content
With the WASM engine, a grid track sized a fill child by its minimum
width alone, so a fill child that is itself a grid shrank to its cell
and its content overflowed it. The CLJS engine sizes the track by the
larger of that minimum and the size the child's content needs, as CSS
gives a grid item its min-content size (user decision: match CLJS).

`min_size` now takes, for a fill grid child, its content size: its
tracks at the sizes its children need, its gaps and its paddings, as a
grid that hugs sizes itself.

Found by the WASM replay of the pinned generated programs (program 290,
a fill grid turned 45 degrees in a grid), which passes with it.

Test: render-wasm `test_a_fill_grid_child_takes_the_size_its_content_needs`.

WASM only; the benchmark covers JVM code and is not run.

AI-assisted-by: claude-opus-5-5
2026-11-18 10:29:50 +01:00
..
2026-03-18 18:05:30 +01:00
fmt
2026-11-09 16:23:47 +01:00
2026-11-09 16:23:47 +01:00
2026-11-09 16:23:47 +01:00

Penpot WASM render

This is the canvas-based WebAssembly render engine for Penpot.

Rust & Emscripten

This project is a Rust crate that targets Emscripten (wasm32-unknown-emscripten).

We use wasm32-unknown-emscripten compilation target:

  • It compiles Rust code into WASM
  • It generates the JavaScript code (“glue”) to load and run the WASM code

How Rust, Emscripten, and WASM are connected

Skia

We use Skia, an Open Source 2D graphics library. In particular, the render engine uses Skia via custom binaries of the rust-skia crate.

How to build

With the Penpot Development Environment running, create a new tab in the tmux.

cd penpot/render-wasm
./build

You can also use ./watch to run the build on every change.

The build script compiles the project and copies the .js and .wasm files to the app that uses each target.

Render targets

The same Rust source produces two artifacts, which differ only in compiler options:

Target Tuned for Cargo profile Consumed by
frontend speed release (-O3) frontend/resources/public/js
export size size (-Oz) exporter/resources/wasm
./build            # both targets, frontend first
./build frontend   # workspace / viewer renderer
./build export     # headless exporter renderer

./watch still follows a single target (frontend unless you pass one), since watching both would rebuild twice on every keystroke.

Each target keeps its own CARGO_TARGET_DIR (target/<target>), so switching between them does not invalidate the other's cache. Set BUILD_MODE=release (or NODE_ENV=production) for an optimized build; the default is debug.

Set PENPOT_WASM_PREPARED=1 when the pinned Rust toolchain is selected, its Emscripten target is installed, and this package's Node dependencies are installed. ./build, ./test, ./lint and ./fmt then skip rustup setup and pnpm install. Benchmark preparation sets this flag for each retained build.

Serialize builds in one checkout

All targets in one checkout share one flock lock stored at render-wasm/.render-wasm-build.lock. The lock covers dependency setup, the Cargo build, artifact copy, and target cleanup. If another build or cleanup already holds the lock, the new process prints a waiting message and starts only after the first process exits.

The watch command takes the lock for each build, then releases it while it waits for source changes. The lock file stays in the checkout after a build, but the operating system releases its lock when the process exits, including after an error or signal.

The lock applies to one checkout and only to commands that use these scripts. A manual Cargo build can still write to the same target without taking the lock. Set RENDER_WASM_LOCK_FILE to the same path in each process when you make different checkouts share a CARGO_TARGET_DIR. The supported Linux build environment must provide flock from util-linux; flock --version checks this dependency.

Use the target cleanup commands instead of running cargo clean on the shared target/ directory:

./clean frontend   # remove target/frontend only
./clean export     # remove target/export only

Each target writes its own generated shared.js (the enum discriminants the CLJS side compiles against) next to the code that imports it — respectively frontend/src/app/render_wasm/api/shared.js and exporter/src/app/wasm/shared.js. Neither build writes to the other's paths.

Architecture overview

Edit your local frontend/resources/public/js/config.js to add the following flags:

  • enable-feature-render-wasm to enable this render engine.
  • enable-render-wasm-dpr (optional), to enable using the device pixel ratio.

How to test

We currently have two types of tests:

  • Unit tests
cd penpot/render-wasm
./test

Technical documentation