You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Just created a brand new NextJS V15 (same happens on V14) and installed tailwind.
If using turbopack (--turbo on npm run dev) tailwind is generating invalid syntax code
Error does not happen when using webpack. (turbopack check for this invalid syntax)
You can even test on code that is commented out due to the compiler scanning possible tokens
That throws an error
On v3.X, I was able to use brackets syntax dynamically all over the code.
I understand that it got changed, and we should use complete class names but should this token be created in first place?
The text was updated successfully, but these errors were encountered:
Yeah indeed. That's something we're looking into right now by improving your scanner. Going to close this as a duplicate but please follow #15853 for updates very soon. Thanks!
What version of Tailwind CSS are you using?
v4.0.6
What build tool (or framework if it abstracts the build tool) are you using?
NextJs
What version of Node.js are you using?
v22
What browser are you using?
Chrome
What operating system are you using?
Windows
Reproduction URL
https://github.com/brunnobb/nextjs-tailwind4-error
Describe your issue
Just created a brand new NextJS V15 (same happens on V14) and installed tailwind.
If using turbopack (--turbo on npm run dev) tailwind is generating invalid syntax code
Error does not happen when using webpack. (turbopack check for this invalid syntax)
You can even test on code that is commented out due to the compiler scanning possible tokens
That throws an error
On v3.X, I was able to use brackets syntax dynamically all over the code.
I understand that it got changed, and we should use complete class names but should this token be created in first place?
The text was updated successfully, but these errors were encountered: