We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
(repost from nuxt/nuxt#7197)
v2.12.2
https://github.com/MZanggl/nuxt-tailwind-config-purge-bug
Running npm run dev you will see the page displaying a blue background. This is because I added
npm run dev
bodyAttrs: { class: 'bg-blue-200' }
in nuxt.config.js.
nuxt.config.js
Running npm run generate and opening the generated files just returns a white background as the class bg-blue-200 got purged.
npm run generate
bg-blue-200
classes inside nuxt.config.js get detected by purgeCSS.
purgeCSS does not take class names in nuxt.config.js into consideration so it accidentally purges these classes.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
(repost from nuxt/nuxt#7197)
Version
v2.12.2
Reproduction link
https://github.com/MZanggl/nuxt-tailwind-config-purge-bug
Steps to reproduce
Running
npm run dev
you will see the page displaying a blue background. This is because I addedin
nuxt.config.js
.Running
npm run generate
and opening the generated files just returns a white background as the classbg-blue-200
got purged.What is expected ?
classes inside nuxt.config.js get detected by purgeCSS.
What is actually happening?
purgeCSS does not take class names in nuxt.config.js into consideration so it accidentally purges these classes.
The text was updated successfully, but these errors were encountered: