Description
Command
build, serve
Description
Reviving #21559, as I'd like to see the same thing implemented, to always have a clear view of what is actually an error and what has already been addressed. Without this it's very confusing to scroll back and forth to see where the last batch of errors are starting, and what was the output from the last build.
Description of #21559 below:
When I'm refactoring large code-base i revised folowing process:
i have ng serve running
i do some changes in bulk without save
save all
i stop the process
clear the console
then start the ng serve again
I'm doing this to see in isolation what I break, fixed what are new issues etc. So I can focus only on what is relevant
Describe the solution you'd like
it would be nice to have a switch to run ng serve which would clear console everytime it detects change
Describe alternatives you've considered
Currently I'm doing it manually - stopping the process, clearing console and starting ng serve again