-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Switch to suppress verbose build output? #1872
Comments
Hey Alan! We've had this feature request before, I think we should add it, would you like to help us? It would involve a small CLI change and a webpack config change. If so, please use the release/3.3 branch as your base 👍 🙇 |
I could take a look. Where in the codebase does |
Here's our guide to contribute: Here's the code points your need: https://github.com/storybooks/storybook/tree/release/3.3/app/react-native/src/bin https://github.com/storybooks/storybook/blob/release/3.3/app/react/src/server/index.js https://github.com/storybooks/storybook/blob/release/3.3/app/vue/src/server/index.js
I hope this helps, |
@ndelangen I changed all the links to point to |
How could we go about overriding the build output via webpack.config.js? I'm in full control mode and attempting to override it with |
@mmmeff What you need to do is filter out the ProgressPlugin if you want to remove it that way. |
@ndelangen Since webpack's plugins field is defined as an array, removing that plugin is less than ideal. Here's my working but sloppy fix for disabling the progress output.
Got a better suggestion? And before I forget, your comment definitely did help me out, so massive thanks for you are in order :) |
@mmmeff does |
@Hypnosphi That did the trick, thanks boss. For posterity, here's the configuration (simplified) to remove the progress plugin and quiet the log spam:
|
@mmmeff Is there a PR for that change? :D |
@alanhogan No. You can add the above configuration to your own webpack.config.js in your .storybook directory though. |
Oh you don’t say… cool… i'll have to give that a go, thanks! |
@alanhogan These docs should help you out https://storybook.js.org/configurations/custom-webpack-config/#full-control-mode-default |
Thanks for helping out @mmmeff ! |
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 60 days. Thanks! |
Hey there, it's me again! I am going close this issue to help our maintainers focus on the current development roadmap instead. If the issue mentioned is still a concern, please open a new ticket and mention this old one. Cheers and thanks for using Storybook! |
Related: #1108 |
Released as |
Our project added storybook's
start-storybook
command to ourProfile
so we can start it and a couple other servers withnf
(Foreman).This works great but builds cause an extreme amount of output in this manner:
Would it be possible for the CLI to take a switch (maybe
--quiet
) that would suppress verbose/progress update messages?The text was updated successfully, but these errors were encountered: