CLI: Pass --quiet to disable HMR logging in browser console

[niedzielski]

Issue: #8461

Pass the CLI --quiet option to the hot module replacement client
instead of hardcoding it in development builds. A minor improvement to
60961d3 (#9535).

#8461 (comment)

What I did

Pass --quiet to webpack-hot-middleware/client. Default to true.

How to test

Pass --quiet to start-storybook and HMR messages should disappear.

• Is this testable with Jest or Chromatic screenshots?
• Does this need a new example in the kitchen sink apps?
• Does this need an update to the documentation?

If your answer is yes to any of these, please make sure to include it in your PR.

[niedzielski]

I believe this is a false positive:

npm notice created a lockfile as package-lock.json. You should commit this file.


Failing the build, there is 1 fail.
Request failed [403]: https://api.github.com/repos/storybookjs/storybook/issues/11087/comments
Response: {
  "message": "Resource not accessible by integration",
  "documentation_url": "https://developer.github.com/v3/issues/comments/#create-a-comment"
}
Feedback: undefined

[shilman]

This looks reasonable to me. I'm assuming errors still show up?

[niedzielski]

@shilman, I should have done more research. Sorry about that. What I'm seeing is that this will suppress all warnings too. I believe errors are always logged but there's some inconsistencies in the logging (e.g., see the warning checking in process-update).

There's a noInfo option I could use instead that will still present warnings. Would that be preferable?

[shilman]

Try it? As long as it’s opt in, we can do whatever you think is most useful

[niedzielski]

Thanks, @shilman! I've passed the quiet option to noInfo instead in a new commit as both warnings and errors are useful to me. Feel free to revert if that's ultimately unwanted.

[shilman]

Looks good @niedzielski! I'll let @ndelangen take a look before merging

[niedzielski]

Yay! Thank you, @shilman and @ndelangen!