Responsive modifiers not working without ! important

[awais019]

What version of Tailwind CSS are you using?
4.1.7
For example: v4.0.6

What build tool (or framework if it abstracts the build tool) are you using?
Nuxt 3.17.3
For example: postcss-cli 11.0.0, Next.js 15.1.7, Vite 6.1.0

What version of Node.js are you using?
23.9.0
For example: v20.0.0

What browser are you using?
Chrome
For example: Chrome, Safari, or N/A

What operating system are you using?
macOS
For example: macOS, Windows

Reproduction URL

A Tailwind Play link or public GitHub repo that includes a minimal reproduction of the bug. Please do not link to your actual project, what we need instead is a minimal reproduction in a fresh project without any unnecessary code. This means it doesn't matter if your real project is private/confidential, since we want a link to a separate, isolated reproduction anyways.

A reproduction is required when filing an issue — any issue opened without a reproduction will be closed and you'll be asked to create a new issue that includes a reproduction. We're a small team and we can't keep up with the volume of issues we receive if we need to reproduce each issue from scratch ourselves.

Describe your issue

Describe the problem you're seeing, any important steps to reproduce and what behavior you expect instead.

Reponsive modifiers like sm md are not working I apply ! important to that utility

[wongjn]

Please consider providing a Tailwind Play link or public GitHub repo that includes a minimal reproduction of the unexpected behavior.

[awais019]

Here you go. https://github.com/awais019/tailwindcss-issue

[wongjn]

Seems to work as expected for me:

[awais019]

Seems to work for me as well now. But for my other project is doesn't work

[wongjn]

Consider providing the other project that doesn't work.

[awais019]

I wish I could but that’s a private repo

…

On Thu, 5 Jun 2025 at 10:55 PM, Justin Wong ***@***.***> wrote: Consider providing the other project that doesn't work. — Reply to this email directly, view it on GitHub <#18230 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASAUBDT3H4BFJUXPG2CLZ6D3CCABJAVCNFSM6AAAAAB6V3J2IOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMZYGI3TKNY> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[wongjn]

You could make a copy with the private bits removed. Or at least, you can debug yourself by removing bits until it works again.

[awais019]

I tried reinstalling and setting up the tailwindcss nothing seems to work

…

On Thu, 5 Jun 2025 at 10:58 PM, Justin Wong ***@***.***> wrote: You could make a copy with the private bits removed. Or at least, you can debug yourself by removing bits until it works again. — Reply to this email directly, view it on GitHub <#18230 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASAUBDQPQNKPQ5IC27MBFDD3CCAMPAVCNFSM6AAAAAB6V3J2IOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMZYGI3TSOA> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[wongjn]

You can try debugging yourself by removing bits until it works again. Or otherwise, consider providing a git repo that includes a reproduction of the unexpected behavior.