-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue with latest tailwind (4.0.8) - styles disappear / not generated by tailwind #603
Comments
@tajo Same issue here. Can we please fix this asap? It's an important issue. |
Same |
Seeing this as well. Reverting to 4.0.6 did not resolve this for me. |
Have the same problem. Can anyone help? |
I found a temporary solution. You need to create a css file inside .ladle and import tailwind example don't forget to import index.css into ./ladle/components.tsx UPD: enough to specify in |
|
The issue
I am using tw4 in my vite project, with vite plugin. In the project itself it works as expected. In ladle it used to work before, but all of a sudden it stopped (still works in main app tho) after I updated my deps - tailwind just does not generate the styles needed by components, but generates ones used by ladle (added via
.ladle/components.tsx
.There is nothing specific about ladle's config, it uses the same configs and roughly same styles as the main app.
Not sure if it is a ladle issue - or rather a tailwind issue, but as main app works and ladle doesn't - I suppose there is something specific either with ladle or how I am using it.
Workaround
Reverting
tailwindcss
and@tailwindcss/vite
from4.0.8
back to4.0.6
and locking versions helps.Reproduction
Was unable to start it in stackblitz (as tailwind apparently needs a native extensions, and they are forbidden in stackblitz)
Therefore I created a repo: https://github.com/andrienko/ladle-issue-reproduction
(it is a stripped down version of my setup, with all important stuff remaining, in case something is wrong with my setup)
Environment
Reproduces on windows 11 / macos ventura / arch 2025.02.01, and in latest chrome/firefox.
Doubt the environment is relevant
The text was updated successfully, but these errors were encountered: