Make a report of classes that are found, included and excluded

[slevy85]

My need is that I want to include only the daisyui styles that I use. For this I use the directive "include" which is great, but it is very hard to be sure that I didn't miss something.

If Daisyui could tell me "Tailwind found this utility class in your code but we didn't include it because it is not in the include directive" (or because it is in the exclude directive), that would be great.

My particular use case is that I have an internal design system based on daisyui, it contains all daisyui classes, and in my apps I need to either

• include all source files
  @source ../packages/my-design-system/**/*.tsx
• list all components that I use

@source ../packages/my-design-system/button.tsx
@source ../packages/my-design-system/modal.tsx
@source ../packages/my-design-system/drawer.tsx

First solution gives too much unused css, the second solution is okay but cumbersome and error-prone.
Using "include" is a good alternative, especially if it provides a report of included/excluded.

Thank you for this great library.

[yudin-s]

This would be very useful, especially for design-system packages where the source boundary is bigger than the app actually uses.

I would frame the report around decisions daisyUI already made during generation, for example:

daisyUI include/exclude report

included:
  btn        found in packages/ds/button.tsx
  modal      found in packages/ds/modal.tsx

found but excluded:
  drawer     found in packages/ds/drawer.tsx, not in include list
  dropdown   excluded by config

configured but unused:
  carousel   listed in include, not found in scanned sources

That would help in three different cases:

• catching missing include entries before UI breaks
• removing unused included components to keep CSS smaller
• debugging @source boundaries in monorepos

I would keep it as an opt-in diagnostic command/flag rather than normal build output, because large apps could generate noisy reports. But as a CI check for internal design systems, it would be excellent: fail the build when a daisyUI class is found in source but excluded from the generated CSS.