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
What build tool (or framework if it abstracts the build tool) are you using?
tailwindcss-cli
What version of Node.js are you using?
none
What browser are you using?
N/A
What operating system are you using?
Windows
Describe your issue
Working on a legacy project I had problem getting utility classes generated from some files but not others, even when located next to each other. It turned out after a lot of hair pulling that the problematic files where encoded in UTF-16 with BOM. Converting all files to UTF-8 fixed the problem.
Sugestion: At minimum show an error message when a file can't be processed.
The text was updated successfully, but these errors were encountered:
Hello,
I ran into a similar issue where Tailwind CSS wasn't generating utility classes from some files, even though they were next to each other. After some troubleshooting, I discovered that the problematic files were encoded in UTF-16 with BOM. Converting them to UTF-8 fixed the issue. It would be really helpful if Tailwind displayed an error message when it can't process a file due to encoding problems.
What version of Tailwind CSS are you using?
tailwindcss-cli v3.4.16
What build tool (or framework if it abstracts the build tool) are you using?
tailwindcss-cli
What version of Node.js are you using?
none
What browser are you using?
N/A
What operating system are you using?
Windows
Describe your issue
Working on a legacy project I had problem getting utility classes generated from some files but not others, even when located next to each other. It turned out after a lot of hair pulling that the problematic files where encoded in UTF-16 with BOM. Converting all files to UTF-8 fixed the problem.
Sugestion: At minimum show an error message when a file can't be processed.
The text was updated successfully, but these errors were encountered: