Dany Castillo

@G9000 you generally don't need to configure colors in tailwind-merge. tailwind-merge will detect all classes that look like color classes and are not known to tailwind-merge as color classes. ```ts...

@Sliov your case is indeed a bug. I created a new issue for it in https://github.com/dcastil/tailwind-merge/issues/391 and am going to close this one to keep things organized. For the others:...

Basically this: https://github.com/dcastil/tailwind-merge/blob/v1.14.0/src/lib/default-config.ts#L90

Also the opacity theme group should only check for `isArbitraryValue` (e.g. by `getNumberAndArbitrary()`) since those classes are never ambiguous.

I could also add installation instructions to the guide page which was requested in https://github.com/dcastil/tailwind-merge/discussions/232.

Possible things to explain in guide: - How to install library - How to set up tailwind-merge in general - How to set up extended scales in Tailwind config -...

Quite like the documentation website of Effect: https://effect.website/docs/introduction

Would it be feasible to switch from Parcel to Rollup to build the react-spectrum packages? I use Rollup to build tailwind-merge ([Rollup config](https://github.com/dcastil/tailwind-merge/blob/v2.5.2/scripts/rollup.config.mjs)) and it preserves all internal names, only...

So far I'm thinking of a new exported function like `createTailwindMergeUtils` or `extendTailwindMergeUtils` or so that exports a bunch of util functions to get all the information that tailwind-merge uses...

One idea is to allow to replace the `splitModifiers` function call in https://github.com/dcastil/tailwind-merge/blob/v2.3.0/src/lib/merge-classlist.ts#L23-L28 (I'd rename it to something like `splitClassName` or `getClassNameParts`). That could unlock some powerful low-level functionality.