Support for twin.macro in tailwindcss-multiple-classes

[1821746019]

Hi there,
First of all, fantastic work on this repo! 🎉 It’s incredibly useful and well thought out.

I was wondering if you'd consider adding support for twin.macro?

I’m working on a Vite project using React, twin.macro, and Emotion. I followed the Vite installation guide provided in your documentation, but it seems like it doesn’t work seamlessly with twin.macro.

Here’s the link to the twin.macro repo for reference:
https://github.com/ben-rogerson/twin.macro

Let me know if I can help with debugging or testing any updates. Thanks again for your amazing contribution to the Tailwind CSS ecosystem!

[MrOxMasTer]

Hi there, First of all, fantastic work on this repo! 🎉 It’s incredibly useful and well thought out.

Hello, thank you for your review. This is my first self-written lib, so it is very unexpected and pleasant.

I was wondering if you'd consider adding support for twin.macro?
I’m working on a Vite project using React, twin.macro, and Emotion. I followed the Vite installation guide provided in your documentation, but it seems like it doesn’t work seamlessly with twin.macro.
Here’s the link to the twin.macro repo for reference: https://github.com/ben-rogerson/twin.macro

I haven't tested with twin.macro, so I didn't know about possible side effects that may occur with this library. But I think it's definitely possible to add support for it when I have time and figure out twin.macro

Let me know if I can help with debugging or testing any updates. Thanks again for your amazing contribution to the Tailwind CSS ecosystem!

In fact - the library implementation is quite primitive and not complicated. It literally fits into one file.

I don't have a lot of time at the moment so I won't be able to do it quickly, but you could try making a pull request and I'll add it to the main thread.

I have long had the idea to add templates to this library that it would compile, such as: cva, cn, css``, class, classname that would be less chaotic.

I would also like to add a blacklist of files and directories that would not need to be compiled (skipped), such as configurations (or left to the user's choice). Because for now it is static and blacklist works only on node_modules.

I plan to implement all this in the future, if tailwind CSS doesn't spring a surprise and suddenly roll out this feature sooner.

[MrOxMasTer]

The problem is that I don't get an AST tree for js/ts files, but for CSS I do (postcss does). So the css files and their @apply directive have the most accurate work. Although maybe I'm not good at webpack and vite configurations and maybe they provide this AST tree which would be easy to manage, so I as vs code, use regular expressions for this library. I'll try to look into this a little later on

[1821746019]

Hi @MrOxMasTer,

Thank you for the quick response and for being open to adding twin.macro support. Unfortunately, I won’t have the time to delve into the code or submit a PR right now. However, I’d still recommend looking into @babel/parser (or similar Babel tools) to handle the AST for JS/TS files if you decide to implement twin.macro support in the future. It could potentially make parsing more robust than regex-based approaches.

I’d be happy to test any future updates if you integrate twin.macro, so feel free to let me know if there’s anything I can help with later on. Thanks again for all your hard work on tailwindcss-multiple-classes!