-
Notifications
You must be signed in to change notification settings - Fork 322
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
Looking for new owner(s) #1044
Comments
@jakubpawlowicz Maybe we can unite? I'm an active developer https://github.com/cssnano/cssnano. |
FWIW, when using the OptimizeCssAssetsPlugin with webpack, with my medium-sized project, Clean CSS is much faster than CSS Nano. Cold builds: Clean CSS CSS Nano More than double (and these builds include Sass, TypeScript, image optimization, etc). Unfortunately the Clean CSS integration in OptimizeCssAssetsPlugin is incomplete (see NMFR/optimize-css-assets-webpack-plugin#87), so I'm forced to use code like this for now. |
@glen-84 i am glad to speedup cssnano 👍 Feel free to investigate, also cssnano should compress better more things |
It would be awesome if you guys could unite to make a real contender to be the best out there. In my team we were using CleanCSS for years (with gulp) before moving to webpack and even though css nano is great, it isnt that fast & the compression is not better so it felt like a downgrade. |
better 😄
yep we are working on this, last version increase speed around 2x-3x Anyway i am glad to union, but @jakubpawlowicz don't give me answer and don't connect with me |
Thanks for the reply ! |
@jakubpawlowicz take a look at https://www.codeshelter.co/ They are a group of volunteers who offer a helping hand for open source projects. Log in with your Github account and add your project. Saw them the other day on Hacker News: https://news.ycombinator.com/item?id=19199647 |
Due to this issue (cssnano/cssnano#712) causing form control validation state icons to render incorrectly.
After long deliberation I'll keep maintaining it for foreseeable future. Wish me luck! |
Hello all,
It's been over 7 years since I started working on clean-css and it has become one of the most popular tools on npm. After spending countless hours on making it a useful tool to you all, I believe a new chapter is around a corner.
Please come forward if you'd like to actively support clean-css, either by writing new features, fixing bugs, or helping others to jump on board.
Speaking on my involvement I'd l like to stay with you until clean-css 5 is released and in the meanwhile gracefully pass the torch to whoever comes next.
So who's interested?
Jakub
The text was updated successfully, but these errors were encountered: