-
-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Global CSS import does not handle backslashes correctly #209
Comments
As for some reason 210 is not merged for a month and 182 is not merged for 6 months, here's temporary fix for arbitary values in Tailwind: ❗️ replace
|
@arkus-pm Thank you for the workaround! ❤️ |
@yuanqing could you merge this / fix this, pretty please? 🙏 |
I wanted to use Tailwind CSS arbitrary values and it did not work correctly with current
create-figma-plugin
implementation.The problem is that Tailwind outputs properly escaped
[
/]
signs in css, but it is not handled correctly in the inline import logic.Consider this
output.css
fileAfter importing it via
import '!./output.css'
we get:Which is incorrect CSS - the
[
/]
values are considered atrribute selectors and not strings.Additional info
Version:
3.1.0
The text was updated successfully, but these errors were encountered: