Pin Vite's deduplication for an application-shaped entry
Plan step 37 review. The Vite test counted each of four files' plain root rule, which the minifier folds into one even when a build repeats the whole stylesheet: it passed against the Workbench's Tailwind entry, which repeated 231 rules. It now asserts that no innermost rule repeats under the same at-rules, which that build fails and a deduplicating one passes, and it builds a second entry shaped like an application's — outside the package, the foundation, then four component stylesheets that each import button.css, and button.css again — where button.css must also keep its first position. The fixture config refuses to run without DEDUP_OUT_DIR, so it never writes into the package tree. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9
This commit is contained in:
co-authored by
Claude Opus 5
parent
3854f4321c
commit
5e7c8b2b58
@@ -0,0 +1,14 @@
|
||||
/*
|
||||
* An application's own CSS entry, the way plan step 37's claim is about: outside the package, the
|
||||
* foundation first, then the stylesheet of each component its views render. Split button, app bar,
|
||||
* modal and pagination each import button.css (and icon.css, through it), and the application
|
||||
* names button.css itself once more at the end. Built by tests/Fixtures/dedup.vite.config.mjs for
|
||||
* StylesheetsBundleTest.php, which expects every shared rule once, at its first position.
|
||||
*/
|
||||
|
||||
@import '../../resources/css/foundation.css';
|
||||
@import '../../resources/css/components/split-button.css';
|
||||
@import '../../resources/css/components/app-bar.css';
|
||||
@import '../../resources/css/components/modal.css';
|
||||
@import '../../resources/css/components/pagination.css';
|
||||
@import '../../resources/css/components/button.css';
|
||||
Reference in New Issue
Block a user