Take Tailwind out of the package, and its detection out of the guard

Tailwind left the stack in 2.0.0, but the package still carried about 330 mentions of it. What the guard's Tailwind detection protected — a class that compiles to nothing — is now protected by a check that does not care where a dead class came from. DesignGuard: about 500 lines of Tailwind tables, scales, palettes and "2.0.0 replacement" hints give way to one check — a class a view or PHP file writes that neither the application's stylesheets nor the package's own declare. It catches a utility of any framework, a typo and a class whose rules were deleted alike, so it also found two classes ReStride draws nothing with. A stylesheet has to be in reach for it: the `.css` files among the scanned paths, or what the `missingStylesheets()` entry imports. The class reader no longer mistakes an array index for a class list (`$block['base']`), and it reads the array a class helper is given, where it read nothing before. The package's own three Tailwind self-guards go with it. Only their one unique check stays, as a test of its own: every `matchMedia` width in resources/js is an M3 breakpoint. The pagination views are `material.blade.php` and `simple-material.blade.php`; only Laravel's and Livewire's default theme names ever made them `tailwind`. The provider sets `Paginator`'s default views and switches `livewire.pagination_theme` to `material` when it is still Livewire's own default, so no application can forget the config; a theme an application chose, and a component's own `$paginationTheme` or `paginationView()`, still win. The rest is prose: the layer-order guidance for an application that still builds Tailwind, the Tailwind wording in the README, the Boost guidelines and the development skill, and about 25 "this used to be a Tailwind utility" comments, along with every "plan step NN" pointer into a gitignored folder. The reset keeps its credit, and NOTICE now carries it too. Feature suite 1159 passed, Chrome browser suite 299 passed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-17 21:07:39 +02:00
parent 247c596c3a
commit fb7007c976
88 changed files with 649 additions and 1521 deletions
@@ -11,7 +11,7 @@
 * Text is smoothed in grayscale where a platform offers the choice (macOS browsers): Google Sans
 * Flex is drawn for it, and subpixel smoothing thickens its strokes on light text over a dark
 * surface. Every surface the package draws — the showcase, the error pages — is set this way,
- * and so is an application, which drops Tailwind's `antialiased` class with nothing to replace.
+ * and so is an application, with no class of its own needed.
 *
 * In `material.base`, above the reset and below every component and text class.
 */
@@ -2,10 +2,10 @@
 * The reset: what a browser draws before any stylesheet, taken back to a clean start.
 *
 * Rule for rule the reset the components were built on, Tailwind CSS 4's preflight (MIT,
- * © Tailwind Labs, after modern-normalize), so a component looks the same whether an application
- * still builds Tailwind or not: every box `border-box` with a `0 solid` border and no margin or
- * padding, headings and lists unstyled, form controls inheriting font, colour and tracking with no
- * background or radius, media as blocks that never overflow their parent. Three differences:
+ * © Tailwind Labs, after modern-normalize): every box `border-box` with a `0 solid` border and no
+ * margin or padding, headings and lists unstyled, form controls inheriting font, colour and
+ * tracking with no background or radius, media as blocks that never overflow their parent. Three
+ * differences:
 *
 *   - no typeface here: foundation/base.css sets `--md-ref-typeface-brand` on <html>;
 *   - a placeholder is `on-surface-variant`, the colour of M3's text field placeholder (androidx