Source paths and third-party components

Tailwind must discover class candidates in the source files where they appear. Monorepos, shared component packages, generated files, and third-party UI libraries can complicate source detection. If a class is missing only in production or only in a package, inspect the source configuration and build pipeline before adding arbitrary CSS overrides.

For a shared component package, document which source files the consuming app must scan or use the supported source registration mechanism for the installed version. Prefer a reproducible build fix over manually copying generated CSS.

Key Takeaways
  • Inspect source discovery when utilities are missing from production.
  • Monorepos and shared packages need deliberate source configuration.
  • Use the official migration guide for major-version changes.