Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Progress Bar for Builds
See original GitHub issueBug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [X] feature request
Request
The progress indicator when builds are happening is ugly. We should make it pretty w/ a progress bar or something.
It would be nice to have something like ONE of these:
I’m happy to PR if someone approves this.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to create and build a progress bar with Webflow
Three-step progress bar tutorial · Step 1: Add and style container div · Step 2: Add the Call to Action · Step 3:...
Read more >The Power of The Progress Bar as a Usability Feature
Progress bars are visual representations of how much progress a site visitor has made toward accomplishing a specific goal. For example, it might...
Read more >Building a loading bar component - web.dev
In this post I want to share thinking on how to build a color adaptive and accessible loading bar with the <progress> element....
Read more >Building Progress Bars for the Web with Django and Celery
Progress bars are one of the most common, familiar UI components in our lives. We see them every time we download a file,...
Read more >A Complete Guide to Using Python Progress Bars - Built In
Progress Bars Using Progressbar2 ... Python-Progressbar (aka Progressbar2) is an extremely popular and easy to use module. It provides some very ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This came up in our team discussion today. We’d like to give a better UX for builds, and a progress bar is a good way of doing that. Currently we just report the percentage complete as a simple string (“92%”), but a progress bar can make that much nicer.
However, the current reporting is just based on Webpack, which is only one component of
ng build. Also framing it as a percentage makes it seem like a portion of the time of the build, which is very hard to estimate. Displaying “Step 4/9 - Compiling TypeScript” can be much clearer and avoid misleading the user. I filed #19181 to add progress reporting outside of Webpack and get more representative values to users.Once that has landed and we have accurate reporting, we can follow up with a nice progress bar here. For now, the progress bar is blocked on accurate progress reporting just to avoid drawing attention to percentage values that aren’t very representative of the actual compilation.
I suppose it’s not very pretty, no. We use
webpack/lib/ProgressPlugincurrently. I don’t really how useful/practical it would be to have one of those progress indicators though… You can’t really know how much time is left because the different phases can take different amounts of time.