You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking through past issues, it seems like this is a potentially viable solution for customizing the prose plugin; however using .not-prose in this case won't unset styles defined in @utility prose.
It's mentioned a few times in various places, but just to make it clear: as of writing, in order to customize the typography plugin, you must use the Tailwind config.
Hopefully, this issue can help track the state of supporting customizing the prose plugin in a "v4 way".
The text was updated successfully, but these errors were encountered:
IHIutch
changed the title
No way to unset .not-prose plugin customizations for v4
No way to unset .not-prose plugin without using Tailwind config
Apr 23, 2025
IHIutch
changed the title
No way to unset .not-prose plugin without using Tailwind config
No way to unset .not-prose without using Tailwind config
Apr 23, 2025
The :not(:where([class~='not-prose'], [class~='not-prose'] *)) will ensures rules nested underneath it won't match inside .not-prose anymore. Here's how this would look like in your example: https://play.tailwindcss.com/OjxphORR9U?file=css
What version of @tailwindcss/typography are you using?
v0.5.16
What version of Node.js are you using?
v20.15.1
What browser are you using?
Brave Version 1.76.73 Chromium: 134.0.6998.45 (Official Build) (arm64)
What operating system are you using?
macOS 15.1.1 (24B91)
Reproduction repository
https://play.tailwindcss.com/B72CiZiVnw?file=css
Describe your issue
Looking through past issues, it seems like this is a potentially viable solution for customizing the prose plugin; however using
.not-prose
in this case won't unset styles defined in@utility prose
.It's mentioned a few times in various places, but just to make it clear: as of writing, in order to customize the typography plugin, you must use the Tailwind config.
Hopefully, this issue can help track the state of supporting customizing the prose plugin in a "v4 way".
The text was updated successfully, but these errors were encountered: