Saurabh Charde

Any further update on this? @navarasu

@netroy is there any blocker in exporting available types? Or should I open a PR if you are willing to merge it?

`tailwind-merge` needs to be shipped to client (i.e, the user's browser) to resolve conflicting classes. You cannot predict during build time which classes should be merged/removed on the client when...

You can join/merge classes with using just `twJoin` and/or `twMerge`, you probably don't need `clsx`. But if you want an object syntax for defining your conditional classes then `clsx` supports...

Yeah. I encountered this "bug" while trying out locomotive v5. I wonder why defining `defaultLenisOptions` outside the constructor is even needed (assuming no function/method is using it outside of the...

I'm also facing somewhat related issue, where I have a snippet like this: ```lua s( { trig = "import", name = "Import Name" }, fmt('import {} from "{}";', { c(2,...

> @Mitsunee Do you have an example of a lib using the `exports` approach successfully where the tree-shaking is working perfectly inside Next? That would be really helpful in updating...

Yep. Having the same issue. I have the exact same setup as @coralof although I'm on Arch Linux + GNOME 46.1.

@devenini If (for some reason) this is not an ideal solution then could you at least ship non-minified files? I could easily patch source files instead of maintaining my own...