Skip to content

Monorepos & multi-brand

Config discovery walks up from each linted file and stops at the nearest dscheck.config.json — so packages can carry their own systems:

repo/
├── packages/app/
│ ├── dscheck.config.json → { "tokens": ["src/theme.css"] }
│ └── src/…
└── packages/marketing/
├── dscheck.config.json → { "tokens": ["brand.css"] }
└── src/…

A file with no config in scope falls back to zero-config discovery at its package boundary (package.json/.git), and a package with no token source at all is not linted — dscheck never enforces a system that isn’t there.