schema.json vs class.json diff

Generated-by-hand companion to bun tools/gen-schema.js.

fixtures/schema.json is the union of the ten documented classnames: groups in vendor/daisyui/packages/docs/src/routes/(routes)/components/*/+page.md. The comparison set is the union of every vendor/daisyui/packages/daisyui/components/*/class.json, which the daisyUI build produces by running functions/extractClasses.js over src/components/*.css only.

Every class below is a real, verified difference. gen-schema.js exits 1 if a class appears in the diff and is not listed here.

Counts: 7 documented-but-not-in-class.json, 70 in-class.json-but-not-documented.

In schema.json but not in any class.json (7)

Tailwind variants, not CSS classes. packages/daisyui/index.js registers them with addVariant, so extractClasses.js never sees them in a stylesheet.

Defined in src/utilities/, not src/components/, so no class.json is generated for them.

Emitted by a plugin, not by a stylesheet.

In class.json but not in schema.json (70)

Classes owned by another plugin or by plain markup, referenced only inside a daisyUI selector.

Deprecated or undocumented daisyUI classes kept in the CSS.

Third-party calendar library classes styled by calendar.css. The calendar docs page documents only the three library root classes (cally, react-day-picker, vc) as its component group; every class below belongs to the vendored library's own DOM, not to daisyUI. (Cally adds none of these because it is a web component styled through ::part().)

react-day-picker internals, styled under .react-day-picker (25):

Pikaday internals and state classes, styled under .pika-single (23):

Vanilla Calendar Pro internals, styled under .vc (18):