Runtime

MiniFW includes a small browser runtime in full-page documents. Its only job is to keep scoped CSS available after HTMX swaps.

Why It Exists

A partial() or boosted page() response may contain a scoped <style> block needed by its new markup. After HTMX swaps that markup into the existing document, the runtime moves the style into the document head.

Each scoped style has a stable route-derived identifier. The runtime checks that identifier before adding a style, avoiding duplicates across repeated swaps.

Configuration

The runtime is enabled by default. Set config.runtime: false in mini() when an application handles swapped scoped styles itself:

mini({
  config: { runtime: false },
});

Disabling it does not stop CSS scoping or style generation. It only removes the browser-side promotion and deduplication step, so your application must ensure styles from HTMX responses remain available.

For the full request lifecycle, see layout(). For selector rewriting and style placement, see Style Encapsulation.