-
-
Notifications
You must be signed in to change notification settings - Fork 224
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
babel-minify still relevant? #945
Comments
If you are asking whether there are more functional and more stable compression engines available, then you have answered your own question. This project's tight integration with Babel however makes it a promising candidate if more development time is invested. Whether this will happen or not... well trying to divine the open-source crystal ball is a pointless endeavor. |
Keep in mind that babel-minify is marked as beta currently. |
Okay, thanks for the info and clarification. |
Going to write up something for this in a bit (and I'll update the readme to be more clear). I think @bardiharborow has it correct: the general idea makes sense so I don't think we would want to drop it, but currently there isn't enough people working on it so we should just signal that better. edited: #947 |
Is babel-minify still relevant? Because terser is very good, and closure-compiler is still one of the best.
Additionally butternut is not actively developed and has several issues - for example the compression throws errors in projects.
The text was updated successfully, but these errors were encountered: