leptos/examples/counter_isomorphic
Greg Johnston 6931d3904b
remove unnecessary `"openssl"` feature from Actix examples (#480)
2023-02-06 09:10:09 -05:00
..
public Add Favicons to all the examples and standardize on the public folder for public assets 2023-01-09 15:27:52 -08:00
src fix: convert `site_address` to `site_addr` to match `cargo-leptos` (#462) 2023-02-04 16:37:41 -05:00
.gitignore Move the examples out of the workspace, and standardize naming. All of the SSR examples now work with cargo-leptos 2022-12-31 15:52:19 -08:00
Cargo.toml remove unnecessary `"openssl"` feature from Actix examples (#480) 2023-02-06 09:10:09 -05:00
LICENSE Move the examples out of the workspace, and standardize naming. All of the SSR examples now work with cargo-leptos 2022-12-31 15:52:19 -08:00
Makefile.toml Switch examples to `check` instead of `build` (for CI resources) and add missing examples (#437) 2023-02-01 20:36:37 -05:00
README.md Fix CSR with Trunk on hackernews example, remove CSR option from isomorphic example (#369) 2023-01-25 20:15:12 -05:00

README.md

Leptos Counter Isomorphic Example

This example demonstrates how to use a function isomorphically, to run a server side function from the browser and receive a result.

Client Side Rendering

For this example the server must store the counter state since it can be modified by many users. This means it is not possible to produce a working CSR-only version as a non-static server is required.

Server Side Rendering with cargo-leptos

cargo-leptos is now the easiest and most featureful way to build server side rendered apps with hydration. It provides automatic recompilation of client and server code, wasm optimisation, CSS minification, and more! Check out more about it here

  1. Install cargo-leptos
cargo install --locked cargo-leptos
  1. Build the site in watch mode, recompiling on file changes
cargo leptos watch

Open browser on http://localhost:3000/

  1. When ready to deploy, run
cargo leptos build --release

Server Side Rendering without cargo-leptos

To run it as a server side app with hydration, you'll need to have wasm-pack installed.

  1. Edit the [package.metadata.leptos] section and set site-root to ".". For examples with CSS you also want to change the path of the <StyleSheet / > component in the root component to point towards the CSS file in the root. This tells leptos that the WASM/JS files generated by wasm-pack are available at ./pkg and that the CSS files are no longer processed by cargo-leptos. Building to alternative folders is not supported at this time. You'll also want to edit the call to get_configuration() to pass in Some(Cargo.toml), so that Leptos will read the settings instead of cargo-leptos. If you do so, your file/folder names cannot include dashes.
  2. Install wasm-pack
cargo install wasm-pack
  1. Build the Webassembly used to hydrate the HTML from the server
wasm-pack build --target=web --debug --no-default-features --features=hydrate
  1. Run the server to serve the Webassembly, JS, and HTML
cargo run --no-default-features --features=ssr