History

Joseph Cruz 65b7603192 fix(ci): address clippy issue (#2278 ) * fix(ci): address clippy issue * fix(ci): add missing nightly specifications * fix(ci): set all nightly references * chore(ci): do not lint example crates		2024-02-09 16:30:11 -05:00
..
assets	examples: add `ssr_mode_axum` (#575 )	2023-02-25 11:24:24 -05:00
src	remove `cfg-if` from all examples	2024-01-19 14:16:58 -05:00
style	examples: add `ssr_mode_axum` (#575 )	2023-02-25 11:24:24 -05:00
.gitignore	examples: add `ssr_mode_axum` (#575 )	2023-02-25 11:24:24 -05:00
Cargo.toml	chore: minimize features activated with `leptos_axum`'s default feature (#1846 ) (#2213 )	2024-01-21 15:22:46 -05:00
LICENSE	examples: add `ssr_mode_axum` (#575 )	2023-02-25 11:24:24 -05:00
Makefile.toml	build(examples): make it easier to run examples (#1697 )	2023-09-12 10:46:16 -04:00
README.md	docs: make it easy to see how to run each example in its README (#2085 )	2023-11-28 11:47:56 -05:00
rust-toolchain.toml	fix(ci): address clippy issue (#2278 )	2024-02-09 16:30:11 -05:00

README.md

SSR Mode Axum Example

This example shows the different "rendering modes" that can be used while server-side rendering an application.

Getting Started

See the Examples README for setup and run instructions.

Server-Side Rendering Modes

Synchronous: Serve an HTML shell that includes fallback for any Suspense. Load data on the client, replacing fallback once they're loaded.
- Pros: App shell appears very quickly: great TTFB (time to first byte).
- Cons: Resources load relatively slowly; you need to wait for JS + Wasm to load before even making a request.
Out-of-order streaming: Serve an HTML shell that includes fallback for any Suspense. Load data on the server, streaming it down to the client as it resolves, and streaming down HTML for Suspense nodes.
- Pros: Combines the best of synchronous and async, with a very fast shell and resources that begin loading on the server.
- Cons: Requires JS for suspended fragments to appear in correct order. Weaker meta tag support when it depends on data that's under suspense (has already streamed down <head>)
In-order streaming: Walk through the tree, returning HTML synchronously as in synchronous rendering and out-of-order streaming until you hit a Suspense. At that point, wait for all its data to load, then render it, then the rest of the tree.
- Pros: Does not require JS for HTML to appear in correct order.
- Cons: Loads the shell more slowly than out-of-order streaming or synchronous rendering because it needs to pause at every Suspense. Cannot begin hydration until the entire page has loaded, so earlier pieces of the page will not be interactive until the suspended chunks have loaded.
async: Load all resources on the server. Wait until all data are loaded, and render HTML in one sweep.
- Pros: Better handling for meta tags (because you know async data even before you render the <head>). Faster complete load than synchronous because async resources begin loading on server.
- Cons: Slower load time/TTFB: you need to wait for all async resources to load before displaying anything on the client.

Quick Start

Run cargo leptos watch to run this example.