noNameWEB/livewire-material
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Import the components in the documented installation

Browse Source 
Plan step 37 review. Removing material.css left README.md, the
development skill, UPGRADE.md and the tailwind.css and foundation.css
headers telling an application to import foundation.css, tailwindcss and
tailwind.css in its place. material.css was also what brought layout.css
and components.css, so that install rendered every component unstyled,
and without a layer statement Tailwind's preflight would have outranked
the package's layers.

The skill's snippet is now the Tailwind-free one 2.0.0 ends with: the
foundation, then the stylesheet of each component the views render, or
all.css. README.md, whose layout and prose still assume Tailwind, shows
all.css in its own entry and Tailwind in a second, both opening with the
layer statement, the shape the Workbench now builds; the skill and
UPGRADE.md describe that interim in a sentence.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Qwx5USif3wFFmxtHg5U1g9
This commit is contained in:
Andreas Reinhold / reini
2026-09-15 03:15:05 +02:00
co-authored by Claude Opus 5
parent 5e7c8b2b58
commit 3365730610
5 changed files with 38 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files
UPGRADE.md
+7 -4
View File
@@ -126,10 +126,13 @@ over a colour, use the role directly.
### 6. `material.css` is gone
The 1.x single-import shortcut no longer exists. An application still building Tailwind imports
`foundation.css`, then `tailwindcss`, then `tailwind.css` in its place (see Installation in
`README.md`); one that has already left Tailwind imports `foundation.css` plus the stylesheet of
each component its views render, or `resources/css/all.css` for everything at once.
The 1.x single-import shortcut no longer exists. The package's CSS is plain now and goes in an
entry without Tailwind: `resources/css/all.css` for everything, or `foundation.css` first and then
the stylesheet of each component the views render. An application whose views still write Tailwind
classes builds Tailwind and `tailwind.css` in a second entry, never beside the package's imports,
since `@tailwindcss/vite` would repeat every shared stylesheet; both entries open with
`@layer properties, theme, base, material, components, utilities;` (see Installation in
`README.md`).
### 7. New in 2.0.0