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
Ability to whitelist whole CSS files #919
Comments
I was also looking for this! In my case the issue was that I want to exclude all Datatables (+ plugins) styles from the purging, as it would be impossible to manually find and safelist them one by one. I also tried wrapping the imports like: /* purgecss start ignore */
@import "~datatables.net/...";
/* purgecss end ignore */ But that also doesn't work 😢 Anybody has suggestions? |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This comment was marked as off-topic.
This comment was marked as off-topic.
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
Not stale |
No workarounds so far. This package is unusable to me unfortunately. |
@dmt0 have you used any other package for the same functionality |
I made it work, with Laravel 10 + Vite 4.4 + PurgeCss, with a workaround... |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
bump |
Is your feature request related to a problem? Please describe.
I'm importing an NPM module that includes a CSS file. A lot of the classes in that file are caught by PurgeCSS.
Describe the solution you'd like
A configuration option to whitelist entire files by path.
Describe alternatives you've considered
content
- didn't work.The text was updated successfully, but these errors were encountered: