2.0.0 not purging css?
See original GitHub issueVersion
@nuxtjs/tailwindcss: 2.0.0 nuxt: 2.12.2
Reproduction Link
https://github.com/alexanderjanke/nuxt-ts-tailwind-template/pull/21
Steps to reproduce
- npm run build && npm start
- open website
ctrl
+u
What is Expected?
CSS should be purged
What is actually happening?
CSS didn’t get purged, everything is imported instead.
I hope I didn’t screw up some of the settings… ?
Issue Analytics
- State:
- Created 3 years ago
- Comments:9
Top Results From Across the Web
2.0.0 not purging css? · Issue #101 · nuxt-modules/tailwindcss · GitHub
What is actually happening? CSS didn't get purged, everything is imported instead. I hope I didn't screw up some of the settings... ?...
Read more >css-purge 2.0.0 vulnerabilities | Snyk - Snyk Vulnerability Database
css -purge@2.0.0 vulnerabilities. A CSS tool written in Node JS as a command line app or library for the purging, burning, reducing, shortening,...
Read more >Tailwind css purge removes all dark classes - Stack Overflow
When I enable purging in my tailwind.config.js file, everything is purged as they should, but all of my dark classes get purged too....
Read more >Better Font Awesome 2.0.0 released - page 2 - WordPress.org
Hi all, I just released the latest 2.0.0 Better Font Awesome version. ... Also also, I'm not seeing the latest inline CSS that's...
Read more >Optimizing for Production - Tailwind CSS
Tailwind CSS is incredibly performance focused and aims to produce the smallest CSS file possible by only generating the CSS you are actually...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That’s why I use Yarn and not NPM 👀😁
Okay to summarize:
Did a
rm -rf .nuxt node_modules package-lock.json
Thennpm i && npm run build && npm start
Now it works with npm too! I Just did the same thing yesterday and now it suddenly works 😄Then I did another
rm -rf .nuxt node_modules package-lock.json
followed byyarn install && yarn build && yarn start
Works as well.No idea on why it failed the first 100 times I tried it before opening this issue but now it does. Maybe it’s some super rare edge-case that I cannot pinpoint. Anyways, thanks for the responses and feel free to close this issue 😃