Add unit tests for lib/utils.ts's cn() edge cases: conflicting Tailwind class resolution

[Austinaminu2]

Description

Following up on the already-filed basic `cn()` test issue, add specific coverage for conflicting Tailwind class resolution (e.g. `cn('p-2', 'p-4')` should resolve to a single winning padding class), which is the trickiest and most bug-prone part of a class-merge helper.

Location

`lib/utils.ts:4`

Task

Add test cases specifically for conflicting utility classes of the same category (padding, margin, color, etc.), asserting the merge helper resolves them the same way `tailwind-merge` (or whatever underlying library is used) is documented to.

Good for contributors because

Narrow, well-defined edge case with clear expected behavior to assert against.

[ritachukwuneye]

@ritachukwuneye has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi maintainer, kindly assign this issue this issue to me please.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @ritachukwuneye to this issue.

[Clinton6801]

@Clinton6801 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello boss I'd love to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Clinton6801 to this issue.

[Peaostrel]

@Peaostrel has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

i can handle this quickly

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Peaostrel to this issue.

[Wilfred-code-wq]

@Wilfred-code-wq has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, I’ve reviewed the issue and understand the requirements. I’m confident I can handle it effectively. Kindly assign it to me

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Wilfred-code-wq to this issue.

[abdulwahabmuhsinah86-afk]

@abdulwahabmuhsinah86-afk has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hey I will be glad if you can assign this work to me tonight thank you

ℹ️ Repo Maintainers: To accept this application, review their application or assign @abdulwahabmuhsinah86-afk to this issue.

[dultimateade]

@dultimateade has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Looks like the basic tests are already there, but the conflicting Tailwind class cases are missing. I'd add a few simple tests to make sure classes like p-2 and p-4 merge correctly and behave as expected. I've worked with Tailwind and unit testing before, so this should be pretty straightforward.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dultimateade to this issue.

[koubascott0-web]

@koubascott0-web has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

I would like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @koubascott0-web to this issue.

[drips-wave]

Congratulations, @koubascott0-web! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

🧑‍💻 @koubascott0-web: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊