-
Notifications
You must be signed in to change notification settings - Fork 2
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
Any ways to combine e()
with cn()
orclsx()
?
#4
Comments
Hi, I tried playing around with some ideas I had some experience with. Unfortunately a proper solution would be an AST traversing. EDIT: this won't help much in this case, but you can use: To make it accept other function names. |
The most annoying thing that TW I've tried edit the regex to only match object in the nameReplacer like Anyways, if there are some workaround for this, it will increase the tailwind's DX to be better. Thank you for your reply 💕 |
If you're good enough with Regex, then there would be ways around it... even if it were like saying to start at a comment like Improving that is something on my list, unfortunately, I seem to never find the time to do it. |
First, thanks for creating this plugin! It's nearly 90% perfect for me. ✨
Why 90%:
I use cn() because although the results of
fonts.Gilroy_Sans.variable
andfonts.Sf_Mono.variable
are "string" (see below), but in the TW transform time, it's a variable, so e() will be failed when parsing the object with those two (I mean just the object's styles was not created, the string and fonts are ok), when delete 2 font variables, it works like normal.Infact, this is enough for me, but I want to try to ask if we can do something like:
But, what e() scanned is
...eArgs
; yes, actually the string..eArgs
, not the object. Although the result when I inspect<html />
seems right, no loss classes:Of course the style from the object, which is
all:*
andselection:*
are not appliedI'm using Nextjs 15 with --turbo, not Webpack but I think that's not the problem. Do you have any ideas or some possible thoughts? @Noriller
The text was updated successfully, but these errors were encountered: