Andreas Reinhold / reiniandClaude Opus 5
3854f4321c
Plan step 37 review. @tailwindcss/vite inlines the imports of an entry that uses Tailwind without Vite's skipDuplicates, so with all.css beside @import 'tailwindcss' every shared component stylesheet repeated later in the cascade (231 repeated rules; button.css's hover and disabled rules thirteen times), and every browser test ran against an order no application gets. workbench/resources/css/package.css now holds all.css and the scheme in an entry Tailwind never touches, and app.css keeps Tailwind for the showcase's classes. The built package CSS repeats no rule, and the Workbench's CSS shrinks from 559 to 406 KB. Both entries open with the same layer statement, properties first, because Tailwind hoists that layer to the top of its output; the order is the one the single entry had, whichever the page links first. The showcase's Vite config, vite.config.js and the error page test's probe manifest name the new entry. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9
12 lines
694 B
CSS
12 lines
694 B
CSS
/* The Workbench's Tailwind entry, for the classes the showcase still writes, with explicit sources
|
|
so the plans in docs/ are not scanned for class names. tailwind.css brings the theme and token
|
|
utilities without declaring the tokens a second time. The package's own CSS is package.css, an
|
|
entry of its own (its header says why); the layer statement is the same in both, so the
|
|
`material` layers sit between Tailwind's preflight and its utilities whichever loads first. */
|
|
@layer properties, theme, base, material, components, utilities;
|
|
@import 'tailwindcss' source(none);
|
|
@import '../../../resources/css/tailwind.css';
|
|
|
|
@source '../../../resources/views';
|
|
@source '../../../src';
|