-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[6.12] Console warning: The purge
/content
options have changed in Tailwind CSS v3.0
#855
Comments
Possible workaround: Provide a plugin to + import typographyPlugin from '@tailwindcss/typography'
export default defineNuxtConfig({
devtools: { enabled: true },
modules: ['@nuxtjs/tailwindcss'],
tailwindcss: {
+ config: { plugins: [typographyPlugin] }
}
}) This should have the module revert to inline PostCSS configuration, so the content configuration should evaluate OK. |
purge
/content
options have changed in Tailwind CSS v3.0purge
/content
options have changed in Tailwind CSS v3.0
Planned fix: use Aiming to implement in 6.12.2-nightly in about a week (6.12.1 this week) |
Implemented potential fix on nightly if you'd like to confirm! |
Environment
Happening after 6.12.0
Reproduction
https://stackblitz.com/github/nuxt-modules/tailwindcss/tree/docs-examples/examples/module-authoring
Describe the bug
This is some race condition that is causing content modification from hooks to not be parsed properly when tracked with the proxy in 6.12.0.
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: