Andreas Reinhold / reiniandClaude Opus 5
fb7007c976
tests / feature (8.4) (push) Successful in 2m0s
tests / feature (8.5) (push) Successful in 2m0s
tests / browser (chrome, chromium) (push) Failing after 8m3s
tests / browser (firefox, firefox) (push) Failing after 12m58s
tests / browser (safari, webkit) (push) Failing after 13m8s
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>
15 lines
1.1 KiB
CSS
15 lines
1.1 KiB
CSS
/* The package's CSS for the Workbench, built the way an application builds it: all.css (the
|
|
foundation, every layout and every component stylesheet), showcase.css (the showcase's own
|
|
chrome, so a real Vite build — an error page's fallback-free path, a browser-test probe page's
|
|
`@vite()` — carries it too, even though the showcase's own pages take their CSS from the bundle
|
|
route instead) and the Workbench's scheme, in the one CSS entry the Workbench needs. Vite's own
|
|
CSS pipeline inlines the imports here and keeps a stylesheet several components import once, at
|
|
its first position — the order an application gets.
|
|
|
|
Opens with the same layer statement every package stylesheet does, so the `material` layers hold
|
|
their place whichever file a page links first; an application needs nothing more than this. */
|
|
@layer material.reset, material.tokens, material.base, material.layout, material.components, material.text, material.visibility;
|
|
@import '../../../resources/css/all.css';
|
|
@import '../../../resources/css/showcase.css';
|
|
@import './material-scheme.css';
|