Skip to content
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

Really need a way to minimize/alter build output information #4133

Open
Aaron-Pool opened this issue Jun 11, 2019 · 8 comments
Open

Really need a way to minimize/alter build output information #4133

Aaron-Pool opened this issue Jun 11, 2019 · 8 comments
Labels
feature request intend to implement The team has the intention to implement this feature at some point. Contribution is also welcome. scope: cli-service build

Comments

@Aaron-Pool
Copy link

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

@LinusBorg
Copy link
Member

@Aaron-Pool
Copy link
Author

@LinusBorg, that should be sufficient, yes. Any output from webpack plugins would still be printed, correct? And linters?

The optimal solution in my case would just be a flag that toggles the log(formatStats(...)) statement. But I get that beggars can't be choosers, so I'll take what I can get 😃

@LinusBorg
Copy link
Member

If I'm not mistaken, you should be able to use --silent right now, it's just not public in the sense that it's not documented.

Report back if the kind of output you get with it is ok.

@Aaron-Pool
Copy link
Author

@LinusBorg Yup, looks like what I want. 👍 I can trust this option to stick around, yeah? Even though it isn't documented?

@LinusBorg
Copy link
Member

I think we can use this issue to discuss that we make it public.

It won't disappear spontaneously anytime soon either way.

@LinusBorg LinusBorg added the intend to implement The team has the intention to implement this feature at some point. Contribution is also welcome. label Jun 12, 2019
@Aaron-Pool
Copy link
Author

Great, appreciate the prompt response, @LinusBorg !

@ulyssesdotcodes
Copy link

This seems to be related: vue-cli-service serve --silent shows all tslint warnings and errors. It would be helpful to just show the errors not tslint warnings. Have tried all sorts of vue.config.js options, including those that should affect the webpack-dev-server.

@BevanR
Copy link

BevanR commented Oct 18, 2021

Another use case for this is a multi-tenanted application. We have a more-complex-than-usual vue.config.js that adds pages/entry-points for each tenant. Each build creates 2-5 entries per tenant in the stats output. With several dozen tenants the list of assets stats is huge. But we don't care about that for local development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request intend to implement The team has the intention to implement this feature at some point. Contribution is also welcome. scope: cli-service build
Projects
None yet
Development

No branches or pull requests

4 participants