Crate ssr_rs

Expand description

The crate aims to enable server side rendering on rust servers in the simplest and lightest way possible.

It uses an embedded version of the V8 javascript engine (rusty_v8) to parse and evaluate a built bundle file and return a string with the rendered html.

Currently it works with Vite, Webpack, Rspack and React 18 - Check the examples folder.

Check here the benchmarks results.

§Getting started

[dependencies]
ssr_rs = "0.5.0"

§Example

To render to string a bundled react project the application should perform the following calls.

use ssr_rs::Ssr;
use std::fs::read_to_string;

fn main() {
    Ssr::create_platform();

    let source = read_to_string("./path/to/build.js").unwrap();

    let mut js = Ssr::from(source, "entryPoint").unwrap();

    let html = js.render_to_string(None).unwrap();
   
    assert_eq!(html, "<!doctype html><html>...</html>".to_string());
}

§What is the “entryPoint”?

The entryPoint could be either:

the function that returns an object with one or more properties that are functions that when called return the rendered result
the object itself with one or more properties that are functions that when called return the rendered result

In case the bundled JS is an IIFE or the plain object the entryPoint is an empty string.

// IIFE example | bundle.js -> See vite-react example
(() => ({ renderToStringFn: (props) => "<html></html>" }))() // The entryPoint is an empty string

// Plain object example | bundle.js
({renderToStringFn: (props) => "<html></html>"}); // The entryPoint is an empty string

// IIFE varible example | bundle.js -> See webpack-react example
var SSR = (() => ({renderToStringFn: (props) => "<html></html>"}))() // SSR is the entry point

// Varible example | bundle.js -> See webpack-react example
var SSR = {renderToStringFn: (props) => "<html></html>"}; // SSR is the entry point

The exports results are managed by the bundler directly.

§Example with initial props

use ssr_rs::Ssr;
use std::fs::read_to_string;

fn main() {
    Ssr::create_platform();

    let props = r##"{
      "params": [
           "hello",
           "ciao",
           "こんにちは"
       ]
    }"##;

    let source = read_to_string("./path/to/build.js").unwrap();

    let mut js = Ssr::from(source, "entryPoint").unwrap();

    let html = js.render_to_string(Some(&props)).unwrap();
   
    assert_eq!(html, "<!doctype html><html>...</html>".to_string());
}

§Example with actix-web

Examples with different web frameworks are available in the examples folder.

Even though the V8 engine allows accessing the same isolate from different threads that is forbidden by this crate for two reasons:

rusty_v8 library have not implemented yet the V8 Locker API. Accessing Ssr struct from a different thread will make the V8 engine to panic.
Rendering HTML does not need shared state across threads.

For the reasons above parallel computation is a better choice. Following actix-web setup:

use actix_web::{get, http::StatusCode, App, HttpResponse, HttpServer};
use std::cell::RefCell;
use std::fs::read_to_string;

use ssr_rs::Ssr;

thread_local! {
   static SSR: RefCell<Ssr<'static, 'static>> = RefCell::new(
       Ssr::from(
           read_to_string("./client/dist/ssr/index.js").unwrap(),
           "SSR"
           ).unwrap()
   )
}

#[actix_web::main]
async fn main() -> std::io::Result<()> {
   Ssr::create_platform();

   HttpServer::new(|| {
       App::new()
           .service(index)
       })
       .bind("127.0.0.1:8080")?
       .run()
       .await
}

#[get("/")]
async fn index() -> HttpResponse {
   let result = SSR.with(|ssr| ssr.borrow_mut().render_to_string(None).unwrap());

   HttpResponse::build(StatusCode::OK)
       .content_type("text/html; charset=utf-8")
       .body(result)
}

Structs§

Ssr