CSS "/*!*/ /*!*/" Incorrectly Processed during Optimize (Tailwind CSS) #2503
Unanswered
jsmith
asked this question in
Troubleshooting
Replies: 1 comment 2 replies
-
Thanks for reporting this @jsmith . I don't know enough about this to answer myself but I'll pass on to the project lead to investigate. |
Beta Was this translation helpful? Give feedback.
1 reply
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.
-
Thanks so much for the new optimize logic. It's super great to be able to optimize for different scenarios and is much faster than the webpack alternative.
Anway, I'm currently using Snowpack v3 and running into a CSS issue during the new optimization process. Tailwind CSS uses
/*!*/ /*!*/
in CSS so that minifers resolve that to an empty space. Currently, when optimization is used, this is resolved to a blank string. To be more specific,is being resolved to
but should be resolved to
I think this might be an esbuild issue? I have a reproduction repo and demo that I'll link to below. In the demo, if you open up devtools and switch
--tw-ring-inset: var(--tw-empty,);
to--tw-ring-inset: var(--tw-empty, );
in the "Styles" pane the focus ring will work as expected.Reproduction repo: https://github.com/jsmith/esbuild-tailwindcss-ring-bug
Reproduction demo: https://jsmith.github.io/esbuild-tailwindcss-ring-bug
Related to tailwindlabs/tailwindcss#2889
Beta Was this translation helpful? Give feedback.
All reactions