Replies: 8 comments
-
Do you intend to make purgeCSS a dependency of tailwind in order to make this possible? Or is this something that can work or be ignored based on whether the user has already installed purgecss in their project? |
Beta Was this translation helpful? Give feedback.
-
PurgeCSS would be a new dependency. |
Beta Was this translation helpful? Give feedback.
-
I did something similar with my ng-tailwindcss package. https://github.com/tehpsalmist/ng-tailwindcss/blob/master/lib/purge.js |
Beta Was this translation helpful? Give feedback.
-
I don't think this should live inside Tailwind. It should do one thing – not minify and purge. There are other processing tools for that. |
Beta Was this translation helpful? Give feedback.
-
yeah, having PostCSS already in your toolchain, running tailwind for you, why would you want this css utility library to post-process your css? |
Beta Was this translation helpful? Give feedback.
-
Since PurgeCSS was added as a dependency and the new tailwind config has a |
Beta Was this translation helpful? Give feedback.
-
I wouldn't add minify when there's tools like like https://github.com/jakubpawlowicz/clean-css-cli
|
Beta Was this translation helpful? Give feedback.
-
Summery
This addresses a pain point of using Tailwinds with Create-React-App where the Webpack build process is concealed, or in small projects without build process.
Example
Implementation
Two new options will be added to the build command.
-m
--minify
- Performs minification viaclean-css
-p [glob]
--purge [glob]
- Removes unused css viapurgecss
. Allows for multiple globs to be specifiedBeta Was this translation helpful? Give feedback.
All reactions