stet.config.ts

Everything about a project's Stet integration in one file, read by the Vite plugin, the CLI and your app, so none of them can disagree.

@stetcms/config defines the shape of stet.config.ts and the ladder that resolves it. It has no runtime dependencies and no relative imports, because three different things load it: your build tool under plain Node, the CLI, and your app at runtime when it serves the analytics route.

Your project rarely installs it directly — @stetcms/vite and @stetcms/cli both depend on it — but the types are worth reading.

defineStet

import { defineAnalytics, event } from '@stetcms/analytics';
import { defineStet } from '@stetcms/config';
import { z } from 'zod';

export default defineStet({
  output: 'src/stet.gen.ts',
  analytics: defineAnalytics({
    events: { signup: event({ plan: z.enum(['free', 'paid']) }) },
  }),
});

defineStet returns exactly what it was given. That is the point: a config that declares analytics has a non-optional analytics at its use sites, so the handler and the browser client read it without a null check.

Options

analytics stays opaque in the type (StetConfig<TAnalytics = unknown>) so this package never depends on @stetcms/analytics. Whatever defineAnalytics() returns flows straight through to createAnalytics<typeof config.analytics>.

Where the file is found

With no explicit path, the plugin and the CLI try these in order, relative to the project root, and use the first that exists:

A config is loaded with jiti, so a TypeScript file works whatever your project’s own build setup is. The default export, a named export, or a zero-argument factory returning one are all accepted.

How settings resolve

Every setting is settled by resolveStetConfig, shared so the plugin and the CLI cannot drift. Explicit wins, then the file, then the environment, then the default:

An empty environment variable reads as unset, not as an empty origin.

apiKey resolves to string | undefined, and every caller tolerates the undefined: the plugin warns and leaves your last generated client in place rather than failing your build.

Exports