14 unstable releases (4 breaking)

0.5.1 Apr 5, 2024
0.5.0 Mar 28, 2024
0.5.0-alpha.0 Feb 23, 2024
0.4.3 Dec 7, 2023
0.1.0 Sep 25, 2021

#214 in HTTP server

Download history 197/week @ 2024-02-02 173/week @ 2024-02-09 321/week @ 2024-02-16 530/week @ 2024-02-23 656/week @ 2024-03-01 508/week @ 2024-03-08 621/week @ 2024-03-15 627/week @ 2024-03-22 524/week @ 2024-03-29 635/week @ 2024-04-05 478/week @ 2024-04-12 777/week @ 2024-04-19 561/week @ 2024-04-26 540/week @ 2024-05-03 506/week @ 2024-05-10 427/week @ 2024-05-17

2,148 downloads per month
Used in 7 crates (6 directly)

MIT/Apache

660KB
12K SLoC

Dioxus Server-Side Rendering (SSR)

Render Dioxus to valid html.

Resources

This crate is a part of the broader Dioxus ecosystem. For more resources about Dioxus, check out:

Overview

Dioxus SSR provides utilities to render Dioxus components to valid HTML. Once rendered, the HTML can be rehydrated client-side or served from your web server of choice.

let app: Component = |cx| rsx!(div {"hello world!"});

let mut vdom = VirtualDom::new(app);
let _ = vdom.rebuild();

let text = dioxus_ssr::render(&vdom);
assert_eq!(text, "<div>hello world!</div>")

Basic Usage

The simplest example is to simply render some rsx! nodes to HTML. This can be done with the render_element API.

let content = dioxus_ssr::render_element(rsx!{
    div {
        (0..5).map(|i| rsx!(
            "Number: {i}"
        ))
    }
});

Rendering a VirtualDom

let mut vdom = VirtualDom::new(app);
let _ = vdom.rebuild();

let content = dioxus_ssr::render(&vdom);

Usage in pre-rendering

This crate is particularly useful in pre-generating pages server-side and then selectively loading Dioxus client-side to pick up the reactive elements.

This crate supports hydration out of the box. However, both the client and server must generate the exact same VirtualDOMs - the client picks up its VirtualDOM assuming that the pre-rendered page output is the same. To do this, you need to make sure that your VirtualDOM implementation is deterministic! This could involve either serializing our app state and sending it to the client, hydrating only parts of the page, or building tests to ensure what's rendered on the server is the same as the client.

With pre-rendering enabled, this crate will generate element nodes with Element IDs pre-associated. During hydration, the Dioxus-WebSys renderer will attach the Virtual nodes to these real nodes after a page query.

To enable pre-rendering, simply set the pre-rendering flag to true.

let mut vdom = VirtualDom::new(App);

let _ = vdom.rebuild();

let mut renderer = dioxus_ssr::Renderer::new();
renderer.pre_render = true;

let text = renderer.render(&vdom);

Usage in server-side rendering

Dioxus SSR can also be used to render on the server. You can just render the VirtualDOM to a string and send that to the client.

let text = dioxus_ssr::render(&vdom);
assert_eq!(text, "<div>hello world!</div>")

The rest of the space - IE doing this more efficiently, caching the VirtualDom, etc, will all need to be a custom implementation for now.

Usage without a VirtualDom

Dioxus SSR needs an arena to allocate from - whether it be the VirtualDom or a dedicated Bump allocator. To render rsx! directly to a string, you'll want to create a Renderer and call render_element.

let text = dioxus_ssr::Renderer::new().render_element(rsx!{
    div { "hello world" }
});
assert_eq!(text, "<div>hello world!</div>")

This can be automated with the render_element! macro:

let text = render_element!(rsx!( div { "hello world" } ));

Usage in static site generation

Dioxus SSR is a powerful tool to generate static sites. Using Dioxus for static site generation is a bit overkill, however. The new documentation generation library, Doxie, is essentially Dioxus SSR on steroids designed for static site generation with client-side hydration.

Again, simply render the VirtualDOM to a string using render or any of the other render methods.

Dependencies

~7–15MB
~172K SLoC