-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Upstream tailwindcss 4.0.0-alpha.25 is broken #12880
Comments
I suggest adding a note with a reference to THIS issue and nothing more. We need to fix this and I don't want the above slightly ugly workaround somehow be how it's done around the web; then we fix it and the workaround stops working ... Also, this is alpha software. |
Seems like the TailwindCLI's reading from stdin is broken in the latest alpha. This fails:
This works:
I will try to find a workaround. |
As a workaround for what seems to be a bug in tailwindcss 4.0.0-alpha.25. See gohugoio#12880
#12881 works for me; if you can take it for a spin and confirm, I can make it into a patch release, as I know there are many Hugo alpha tailwind users out there. Also, I will create a upstream bug. |
As a workaround for what seems to be a bug in tailwindcss 4.0.0-alpha.25. See gohugoio#12880
Upstream issue: tailwindlabs/tailwindcss#14521 |
As a workaround for what seems to be a bug in tailwindcss 4.0.0-alpha.25. See gohugoio#12880
This was fixed upstream with tailwindcss 4.0.0-alpha.26. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This works:
This fails:
Alpha 25 was released yesterday:
https://github.com/tailwindlabs/tailwindcss/releases/tag/v4.0.0-alpha.25
I am suspicious of this change:
tailwindlabs/tailwindcss#14446
To reproduce:
build log
I can get 4.0.0-alpha.25 to work by adding an explicit mount:
And then changing the initial import statement from:
To:
Given that we can make this work, perhaps we should address this in the documentation, the example repository, and in the integration test.
The text was updated successfully, but these errors were encountered: