Skip to Content
Read the release notes before upgrading production environments.
CLIConfiguration

Supported config filenames

The CLI scans upward from current working directory for:

  • cms0.config.ts
  • cms0.config.js
  • cms0.config.mjs
  • cms0.config.cjs
  • cms0.config.json
import { defineConfig } from "@cms0/cms0/config"; export default defineConfig({ entry: "./src/data/cms0.ts", tsconfig: "./tsconfig.json", api: { baseUrl: process.env.VITE_CMS0_API_BASEURL, key: process.env.VITE_CMS0_API_KEY, }, });

Field behavior

  • entry (required): file that contains your schema usage
  • tsconfig (optional): explicit TypeScript config path
  • api.baseUrl (optional): endpoint used for descriptor publishing defaults
  • api.key (optional): key used for descriptor publishing defaults

Best practices

  1. Keep config at project root.
  2. Keep entry stable to avoid accidental schema drift.
  3. Use environment variables for sensitive values.