SSG renders pages to static HTML at build time, for deploying to a CDN or any static host without a running server.

Adding SSG Support

SSG is automatically enabled if selected during source folder creation (or via --ssg flag in CLI mode). To add it to an existing folder, register ssgGenerator in your source folder's kosmo.config.ts:

kosmo.config.ts

import {
  defineConfig,
  // ...other generators
  ssgGenerator,
} from "@kosmojs/dev";

export default defineConfig({
  generators: [
    // ...other generators
    ssgGenerator(),
  ],
});

It works on source folders with a frontend and SSR enabled: pages are rendered by the folder's own SSR server.

Declaring staticParams

Static routes (no parameters) render automatically. A dynamic route renders once per parameter set it declares through staticParams; a dynamic route without staticParams is skipped - no file is generated for it.

staticParams is a list of variants, each one positional in the route's parameter order. A splat parameter takes an array of segments.

Where the declaration lives depends on how the framework exposes named exports from a page module:

import { defineStaticParams } from "_/core";

export const staticParams = defineStaticParams<"docs/[slug]">([
  ["getting-started"],
  ["routing"],
  ["validation"],
]);

export default function DocsPage() { /* ... */ }

Values are stringified into the path, so numbers are fine: [[1], [2], [42]] renders items/1, items/2, items/42.

Data loading works as usual - the page's loader runs once per variant, with that variant's parameters, against the API bundled into the SSR server.

React Fast Refresh

A non-component export in a React page file makes Fast Refresh fall back to a full reload for that file during development. It is a development-only nuisance, the build is unaffected.

Output

The build writes a complete static site to dist/<folder>/ssg/:

dist/front/ssg/
├── index.html
├── docs/
│   ├── getting-started/index.html
│   ├── routing/index.html
│   └── validation/index.html
├── assets/              → hashed JS and CSS, the same set the SSR server serves
├── favicon.svg          → public/ files, copied to the root
└── robots.txt

The tree is rooted at the folder's base, same as a Vite client build: a folder with base: "/admin" produces ssg/index.html, ssg/items/1/index.html and so on, and the HTML references /admin/assets/... - deploy the ssg/ directory at /admin/ on the host.

Nothing in the output depends on the ssr/ or client/ directories at serve time.