What problem does this feature solve?

We're developing an app that's behind an enterprise authentication setup (ntlm) that doesn't play well with the yarn dev server (and yes, several people on my team have tried to get around this problem, without long term success). As a result, instead of the preferred yarn serve, we use yarn build --watch during ongoing development. Unfortunately, after every update, the build process displays every chunk that has been generated, which completely pushes useful errors and warnings from the linter offscreen.

As of now, there is no way for a user to disable this build output. I've seen several requests to be able to disable/alter build logging, but it seems like the Vue-cli devs struggle to grasp a tangible example for when this would add substantial value to the user. I understand that--it is, of course, important to prioritize features based on actual value added, so I just wanted to create this issue to give a concrete example where being unable to suppress or minimize build output information substantially frustrates the dev experience. Instead of being able to leave the terminal open in a separate screen and glance at it for linting errors, I have to scroll the terminal back up a full page length every time I save to see any compilation warnings or errors.

What does the proposed API look like?

--verbosity-level none | minimal | debug | default