remix

Mixins created through remix/component can use createMixin(setup, { ssr: false }) to skip setup and render on the server while keeping browser behavior and hydration. Server rendering remains enabled by default. The option is intended for behavior that does not contribute to the server HTML.

Server rendering with remix/component is about twice as fast as in 3.0 and uses less memory, with no code changes. Rendering a 48-product listing page with renderToString() takes 244 µs instead of 513 µs (Node.js 24.18 on an Apple M5 Pro, median of 5 fresh-process runs, identical HTML output). Under sustained HTTP load on a 24-product store page, assembling each response with a single join lowers the server's resident memory after load from 793 MiB to 527 MiB (see #12006, #12016, #12018, and #12020).

Use frame.reload({ src, method, encType, body }) from remix/component to reload another source or submit data and render the response without changing browser history. FormData follows GET query and POST encoding defaults, with multipart and plain-text encodings available.

Prefetch frame HTML and assets with data-rmx-prefetch="intent", data-rmx-prefetch="viewport", or the imperative prefetch() API from remix/component. Both link modes support named frames and source overrides, respect Save-Data, and skip slow-2g/2g connections. See the prefetching guide for usage, customization, and caching behavior.

Installation and new-app examples now use the stable Remix release.