-
-
Notifications
You must be signed in to change notification settings - Fork 27k
Reviving Add BuildProgressPlugin #6310
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
Comments
I think we should abandon this pr and create a new one that use this plugin instead: https://github.com/clessg/progress-bar-webpack-plugin |
I'll let @Timer chime in on this one, as I wasn't across it in detail. If there's a newer, more accurate version, that could also be good to discuss. By the way, "back in January, 2019" is scary to say so soon ;) |
You caught me :-) January 2018 |
I'm fine with you working on it @eladmotola |
This issue has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs. |
I never got a chance to work on it but would like this to stay open |
I'm going to label this as "Up for grabs" unless you think you'll have time to work on it in the near future. |
I'd like to dig into this if possible. Would acceptance criteria for this look like getting the webpack ProgressPlugin to work? |
I just learned that enabling any of these progress plugins introduces a significant performance penalty in webpack. They all require webpack to emit progress information during the build and that slows things down quite a bit. I don't think it's worth it just to display a progress bar so I'm going to close this issue. |
Is this a bug report?
No
I was just wondering if there was any interest in reviving the Add BuildProgressPlugin PR that got closed back in January, 2019
I believe @Timer had it working but wasn't happy with the progress accuracy -> is this still true? not sure if anything has changed but to me it seems like something would be better than nothing
anyone else interested in this? I could try and revive the PR again at some point in the next few weeks
The text was updated successfully, but these errors were encountered: