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>
31 lines
1.3 KiB
JavaScript
31 lines
1.3 KiB
JavaScript
import { defineConfig } from 'vite';
|
|
|
|
// Builds two CSS entries with no plugin in the graph, isolating Vite's own bundled postcss-import,
|
|
// whose `skipDuplicates` option is the deduplication StylesheetsBundleTest.php pins:
|
|
// resources/css/all.css, and tests/Fixtures/dedup-app.css, an application-shaped entry importing
|
|
// per-component stylesheets that share button.css. A stylesheet several files import lands once
|
|
// per entry, at its first position.
|
|
//
|
|
// Not the Workbench's config: this one carries no plugin, which is what isolates Vite's own
|
|
// postcss-import above. The Workbench's config carries laravel-vite-plugin, so its build is not
|
|
// this dedup test's to run.
|
|
//
|
|
// DEDUP_OUT_DIR is required: the test builds into a temporary directory and deletes it, and nothing
|
|
// should land in the package's own tree, least of all workbench/public/build.
|
|
if (!process.env.DEDUP_OUT_DIR) {
|
|
throw new Error('Set DEDUP_OUT_DIR to the directory the dedup fixture should build into.');
|
|
}
|
|
|
|
export default defineConfig({
|
|
publicDir: false,
|
|
build: {
|
|
outDir: process.env.DEDUP_OUT_DIR,
|
|
emptyOutDir: true,
|
|
manifest: true,
|
|
rollupOptions: {
|
|
input: ['resources/css/all.css', 'tests/Fixtures/dedup-app.css'],
|
|
},
|
|
},
|
|
logLevel: 'silent',
|
|
});
|