Replies: 3 comments
This comment was marked as spam.
This comment was marked as spam.
-
|
In Tailwind CSS v4, the standalone CLI no longer supports the --content flag that existed in v3. Instead, content detection is driven by your project configuration. If you're using the standalone binary, could you share your project structure and how you're currently invoking the CLI? That would help determine whether the HTML files are being detected automatically or whether another workflow is needed. |
Beta Was this translation helpful? Give feedback.
0 replies
This comment was marked as spam.
This comment was marked as spam.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
There is
--contentoption intailwindcssversion 3 that allows to feed HTML contentBut it seems not available anymore in tailwindcss v4
I wonder if there is a way to parse HTML files using tailwindcss binary?
Beta Was this translation helpful? Give feedback.
All reactions