-
Notifications
You must be signed in to change notification settings - Fork 44
Consider moving this into webpack/webpack? #1
Comments
Sure. I don't have any concerns where the code lies. I can send a PR. There are a few concerns that I think should be considered -
|
Awesome I'd like to discuss with the core team first their thoughts. I'll followup with you in about a week. Again thank you for the work and flexibility. |
👋 Hi folks. Whatever happened to moving this plugin to webpack/webpack? Cheers. |
We could think about moving this into webpack-contrib |
Any news on the transfer? I understand if you want to retain it under your account. No probs with that. |
Hey. Nothing like that. We can transfer it now. How do we do it ? Do I give you access to the repo ? or do you give me access to the org for the transfer ? |
@boopathi I invited you to the org so you should be able to rename the repo to complete the transfer. Thanks a lot. 👍 |
👍 |
Hey!!! My name is Sean, and I'm one of the core maintainers for webpack. By the way, nice job on creating something so quickly after the release of babili.
Since webpack already owns UglifyJSPlugin, I'd love to see this also moved into our organization, whether it be added as core code, or a repo underneath the org.
The webpack team wants to have optimization stuff as much "Out of the box" as possible for user configuration.
Would you be open to either of these ideas? This will give us a lot more hands on in helping maintain and configuring the plugin for speed and performance, etc.
Let me know what you think. And again thanks for your work.
The text was updated successfully, but these errors were encountered: