question-mark
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.

Provide clear output about when a build finishes

See original GitHub issue

Do you want to request a feature or report a bug?

I’m proposing a feature/enhancement.

What is the current behavior?

When running webpack with --watch for a while, your console is likely to fill with many almost identical blocks of build output with only the chunk hashes being different.

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

After a build has finished, in addition to the build duration, print the current time and the time when the build started to make it easier to tell, if what you’re seeing is a new build or still an old one.

If this is a feature request, what is motivation or use case for changing the behavior?

The almost identical blocks of output make it hard to tell, if a build you just triggered with a file change has already finished.

On projects with long build times (even for incremental builds), I often find myself saving a file in my editor, switching to the terminal where webpack is watching the files and hitting Enter a few times so I can clearly see when the next output block is printed to the console.

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.

  • webpack version: 2.5.1
  • all platforms and node versions

I’d be happy to work on this myself and to hear any alternative ideas.

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:2
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

2reactions
sokracommented, Jul 17, 2017

There is a PR for this: https://github.com/webpack/webpack/pull/5026

You can help finishing it. Tests need to be solved.

0reactions
selfawaresoupcommented, Mar 13, 2018

Yes, this is done.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Why is docker build not showing any output from commands?
When I run docker build . I don't see any output from these two commands even if they are not cached. The documentation...
Read more >
Clear build output before displaying in new result
When executed via the terminal the previous tsc output is cleared before the new results are piped in. When executed via sublime build...
Read more >
Docker Cache – How to Do a Clean Image Rebuild and Clear ...
The most popular container platform is Docker. This tutorial will explain how to use the Docker build cache to your advantage.
Read more >
docker buildx build
Sets the export action for the build result. In docker build all builds finish by creating a container image and exporting it to...
Read more >
POWER PHRASES TO BUILD YOUR RESUME
Provide strong evidence of specific accomplishments ... Achieve high administrative output ... Clearly establish administrative rules and regulations.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found