-
Notifications
You must be signed in to change notification settings - Fork 404
Description
Current behavior 😯
In tailwind 4, which is still only in beta (but it would be good to fix this before they hit stable), there are now two ways to install tailwind.
- Traditional: Using a Postcss plugin - works as expected
- New: Using a Vite plugin (works in astro, but dev server struggle in solid-start)
The vite plugin works as expected when making a prod build, and for the dev server on a clean reload, but if the dev server is restart in solid-start, the style will be broken. To get it working again, it will be necessary to do either of the following:
- delete
node_modules/.vinxiand then restart dev server - modify/re-save
./src/app.css- triggering this file reload is enough to make it work again
With Astro (v5), there are no issues with restarting the dev server using @tailwindcss/vite with Solid.
With TanStack Start (vinxi 0.4.3/0.5.1), there are no issues either.
Expected behavior 🤔
I expected the tailwind plugin to load correctly on dev server restart.
Steps to reproduce 🕹
There's a repo here with multiple implementations:
https://github.com/birkskyum/tailwind-vite-repro
- Astro with Vite plugin (and solid) - working
- TanStack Start with Vite plugin (and vinxi) - working
- Solid Start with Postcss plugin - working
- Solid Start with Vite plugin - breaking after dev server restart
I can reproduce this issue with vinxi 0.4.3 / 0.5.0 / 0.5.1 and overrides with vite 5/6
The working output looks like this:

The broken output will look like this:
Context 🔦
No response
Your environment 🌎
No response