Configuration files

The configuration is the default export of config/default.ts. Files for other environments are merged on top.

import { defineConfig } from 'yassb-web';
import { talkList } from '../builder/renderers';

export default defineConfig({
  customRenderers: { talkList },
  siteHost: 'https://example.com/'
});

defineConfig only adds types; export default { … } as YassbConfig works too (and does not need yassb-web at runtime).

Environments

The config folder is read with the same rules as the popular config package, which YASSB 1 used:

Files are merged in that order: objects deeply, arrays and functions replaced. NODE_CONFIG_DIR changes the folder, and NODE_CONFIG (JSON) is merged last. Extensions: .ts, .js, .cjs, .mts, .cts, .tsx, .json. Other formats (YAML, TOML…) are reported and skipped (CONFIG_UNSUPPORTED_FILE).

TypeScript everywhere

The configuration and everything it imports (renderers, directives, helpers) can be TypeScript or TSX, without installing TypeScript:

• under Node, each file is compiled on its own with esbuild, using your tsconfig.json: __dirname, relative paths and require work as usual, and stack traces point to your TypeScript lines;
• under Bun, TypeScript runs natively;
• types are not checked during the build; run tsc --noEmit for that.

A syntax error is reported with file and line; a missing package is explained, including packages YASSB 1 used to install for you (CONFIG_MODULE_NOT_FOUND).