Pre-rendering Mode (SSG)

Introduced into the version 1.2.0, the Pre-rendering mode, also known as Static Site Generation (SSG), allows Rasengan.js to generate HTML pages ahead of time, during the build process. Instead of rendering pages in the browser (SPA) or on the server at request time (SSR), Rasengan creates static HTML files that can be deployed anywhere—CDN, file storage, or any static hosting provider.

This results in:

• Faster load times (no server needed to generate pages)
• Better SEO, since pages are already rendered for search engines
• More stability, because there’s no runtime server to fail
• Lower hosting cost, as static hosting is usually cheaper

When building your project, Rasengan.js scans specific routes and pre-renders them into static .html files. These files represent your pages exactly as users will see them, without needing JavaScript to generate the initial view.

But to enable this feature, you have first to configure your rasengan.config.js file.

tsimport { defineConfig } from 'rasengan';
import { rasengan } from 'rasengan/plugin';
 
export default defineConfig({
  prerender: true,
  vite: {
    plugins: [rasengan()],
  },
});

Then run the build command.

bashpnpm run build

After running the build, you’ll get a structure similar to:

bash/static
  ├─ index.html
  ├─ about/
  |  └─ index.html
  ├─ contact/
  |  └─ index.html
  └─ blog/
       └─ article-1/
          └─ index.html

Each file is a ready-to-serve static page.

To mark a route for static generation, simply specify the exact route or a generic one to match a set of routes:

tsimport { defineConfig } from 'rasengan';
import { rasengan } from 'rasengan/plugin';
 
export default defineConfig({
  prerender: {
    routes: ['/', 'blog/**'],
  },
  vite: {
    plugins: [rasengan()],
  },
});

Rasengan.js will detect this and include them in the pre-rendering process automatically.

If your page depends on data (like a blog post, product list, or API call), use loader to provide data at build time:

jsx// src/app/_routes/blog.page.jsx => blog.html
 
export default function Blog({ posts }) {
  return (
    <ul>
      {posts.map(post => <li key={post.id}>{post.title}</li>)}
    </ul>
  );
}
 
Blog.loader = async () => {
  const posts = await fetch("https://api.example.com/posts").then(res => res.json());
  return { props: { posts } };
}

The data is fetched once during build, and the generated HTML ships with the content already rendered.

In Rasengan.js, you can statically generate pages that depend on dynamic parameters (like usernames, slugs, or product IDs). This is useful for pages such as:

• User profiles (/users/:username)
• Blog posts (/blog/:slug)
• Product pages (/products/:id)

Instead of generating these pages when the user visits them, Rasengan.js creates the HTML files during the build, one for each parameter.

To pre-render dynamic routes, you need to:

1. Use a dynamic parameter in your page route (for example: src/app/_routes/users/[username].page.tsx)
2. Return a list of paths to generate using generatePaths
3. Access the parameter in the component with useParams()

tsx// src/app/_routes/users/[username].page.tsx
import { PageComponent, useParams, defineStaticPaths } from "rasengan";
 
const Page: PageComponent = () => {
	const { username } = useParams();
 
	return (
		<section className='w-screen h-screen bg-red-300 flex justify-center items-center'>
			Hello {username}
		</section>
	);
};
 
// List of dynamic values to pre-render at build time
Page.generatePaths = async () => {
	return defineStaticPaths([
		{ username: "nina" },
		{ username: "dilane3" },
		{ username: "michel" },
		{ username: "adora" },
		{ username: "donald" },
	]);
};
 
export default Page;

After running the build, Rasengan.js will create one page for each username:

yml/static/users/nina/index.html
/static/users/dilane3/index.html
/static/users/michel/index.html
/static/users/adora/index.html
/static/users/donald/index.html

Each page is fully static and ready to be served.

To preview the static pages, you have first to run the build command.

bashpnpm run build

Then, you need to add a new script into your package.json file or just updating the actual serve command in order to consider the new static folder as the production output. You will always need to use rasengan-serve CLI coming from @rasenganjs/serve adapter to achieve this. It's the same adapter used to preview SPA and SSR apps in Rasengan.js.

json{
  "scripts": {
    "serve": "rasengan-serve ./static"
  }
}

Finally, running pnpm run serve will start the server and you can preview your static pages.

• Instant page load → no waiting for rendering
• SEO-friendly → content is visible immediately
• Scales automatically → no server load per request
• Deploy anywhere → Netlify, Vercel, S3, GitHub Pages, etc.