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
Current implementations of PurgeCSS with Angular require some sort of custom builder (as I understand it), which, in my opinion, is not ideal for large projects with many contributors.
It would be fantastic to have a plugin for Angular, similar to those available for other frameworks (e.g., Next.js, Vue). If a plugin isn't possible, it would be great to have a standard configuration that could be added to angular.json (or project.json in Nx monorepos) to ensure our PostCSS hook is correctly executed after every production build.
Describe alternatives you've considered
Honestly, for my organization, using default builders is a dealbreaker, so we don't even attempt to go down that rabbit hole.
There was a similar request that was closed years ago, but it seems the issue remains unresolved. Any comments or updates on this would be appreciated to help set our expectations.
Thanks for the great work!
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Describe the solution you'd like
It would be fantastic to have a plugin for Angular, similar to those available for other frameworks (e.g., Next.js, Vue). If a plugin isn't possible, it would be great to have a standard configuration that could be added to
angular.json
(orproject.json
in Nx monorepos) to ensure our PostCSS hook is correctly executed after every production build.Describe alternatives you've considered
Honestly, for my organization, using default builders is a dealbreaker, so we don't even attempt to go down that rabbit hole.
There was a similar request that was closed years ago, but it seems the issue remains unresolved. Any comments or updates on this would be appreciated to help set our expectations.
Thanks for the great work!
The text was updated successfully, but these errors were encountered: