fix(css): resolve app.config.ts source to an absolute path

[benjamincanac]

Resolves #1403
Resolves #1399

Problem

In layer/modules/css.ts, the generated docus.css declared:

@source "../../app.config.ts";

This was the only relative path among the CSS sources — every other @source/@import is an absolute filesystem path. Tailwind resolves @source relative to the CSS file that contains it, and that file is generated at <srcDir>/.nuxt/docus.css. So ../../app.config.ts resolved to <rootDir>/app.config.ts — a file that does not exist.

For example, in this repo the generated docs/.nuxt/docus.css contained:

@source "/…/docus/docs/content/**/*";
@source "/…/docus/layer/app/**/*";
@source "../../app.config.ts";   ← resolves to /…/docus/app.config.ts (missing)
@source "/…/docus/layer/modules/assistant/**/*";

The real config lives at <srcDir>/app.config.ts (e.g. docs/app/app.config.ts). As a result, class names declared in the user's app.config.ts (UI theme overrides) were never whitelisted by Tailwind and could get purged.

Fix

Compute an absolute path from nuxt.options.srcDir, consistent with the other sources:

const appConfigPath = resolve(nuxt.options.srcDir, 'app.config.ts')
// …
@source "${appConfigPath.replace(/\\/g, '/')}";

This now points at the user's actual app.config.ts (the same srcDir the app.css import is derived from).

Note: the layer's own app.config.ts (layer/app/app.config.ts) is already covered by the @source "${layerDir}/**/*" glob, so this line only ever needed to target the user's config.

This may also resolve related class-purging issues seen in nuxt-studio.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/create-docus@1404

npm i https://pkg.pr.new/docus@1404

commit: 248a6c0

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docus	Ready	Preview	Jun 24, 2026 10:36am