Replies: 2 comments
-
Consider checking if your input CSS file has been encoded as UTF-8 with BOM. If so, try resaving it with encoding UTF-8. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks for reply. Yes, my source file is encoded UTF-8 with BOM, and changing to UTF-8 prevents the error. I'd hope this would be considered a bug, and Tailwind would not fail on this. At the very least, the error should tell you it refuses to work with BOM encoding? My files in v3 have always been BOM encoded, never had any trouble. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What version of Tailwind CSS are you using?
v4.0.3
What build tool (or framework if it abstracts the build tool) are you using?
@tailwindcss/cli 4.0.3
What version of Node.js are you using?
v22.13.1
What browser are you using?
Chrome
What operating system are you using?
Windows
Describe your issue
Following the installation instructions docs for CLI, step two is to create a css file with content:
@import "tailwindcss";
When I do this an run the build command in step 3, it fails with error:
However, when I remove the semicolon on the import line, build succeeds. This avoids the error:
@import "tailwindcss"
** Expected behavior **
The semicolon should be optional, or the CLI should not fail when it is provided as documented.
Beta Was this translation helpful? Give feedback.
All reactions