Extend tailwind-merge configuration

[stijns96]

For what version of Nuxt UI are you suggesting this?

v2.x

Description

I know you guys are working hard on V3, but I really like to see this feature still in V2. We all know that not everybody will move over to V3 right away.

I have to set my strategy to override, because tailwind-merge doesn't know about my custom tailwind extends. This is quite a pain in the ass, since this is causing other issues as well. Take the Pro LandingGird as example. Classes are added to the grid items to set the right cols. By doing this with strategy set to override, all other classes will be overridden.

I saw some sort of solution in #925 , but that didn't work. It's also not documented and can't find it in the module either.

I know have to create my own merge config, but that will not work for Nuxt UI.

Additional context

You may wonder why I need this. Thats because I'm also using Tailwind Fluid, and try to replicate a design library that uses different spacings etc.

[benjamincanac]

I don't think it's possible at the moment. However, I did this PR back in the days that I ended up not merging that might solve this: #1108

[stijns96]

Hi @benjamincanac ,

Thanks for looking at it. It did see that PR as well.

What are the next steps? I'm a bit confused as you mention it is not possible while that PR might fix the issue?

[benjamincanac]

This could be reopened but a lot has changed meanwhile and the refactor might need to be done on other components as well. I don't have time for this at the moment so feel free to open a PR 😊

[benjamincanac]

Duplicate #1939.

[stijns96]

Hi @benjamincanac,

I'll see what I can do. Just as a reference, the PR seems quite accurate already, right?

Simply change the imports and make sure the twMerge key from the app.config will be merged in there as well.

If you could confirm it will give me a better start 😊

p.s. from what branch should I create a new branch? From main and then PR to dev?

[benjamincanac]

I've restored the fix/925 branch, you can checkout it and merge from dev to resolve the conflicts. Then open a PR from this branch that targets dev.