How to enable [HMR] console logging in 5.2

[dnielbowen]

I'm hesitant to upgrade from 5.1 to 5.2, as it appears Webpack's [HMR] console logging has been disabled. Can this be re-enabled through configuration?

I've tried creating ./.storybook/webpack.config.js with:

module.exports = async ({ config, mode }) => {
  config.devServer = { stats: "verbose" };
  return config;
};

...and an assortment of variations, but no change.

[shilman]

@ndelangen any ideas?

[stale]

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 30 days. Thanks!

[cliffpyles]

I haven't figured out the solution, but I believe I've tracked down what is causing the behavior. From what I can tell the devServer configuration is being passed to Webpack correctly, and the configuration goes to webpack-dev-middleware as intended. The issue is with webpack-hot-middleware though. It allows for a quiet property to be passed and currently it is being set with a true value, which is suppressing output.

storybook/lib/core/src/server/dev-server.js

Line 119 in 87e705d

router.use(webpackHotMiddleware(previewCompiler));

https://github.com/webpack-contrib/webpack-hot-middleware

I hope this helps!

[dnielbowen]

That's it! I'm not seeing an easy way to get to it through configuration, but in the line...

storybook/lib/core/src/server/preview/preview-preset.js

Lines 14 to 16 in a2a6b9d

	result = result.concat(
	`${require.resolve('webpack-hot-middleware/client')}?reload=true&quiet=true`
	);

...changing quiet=true to quiet=false enables the console output again. Thanks!

[cliffpyles]

No problem. Glad you figured out!

[BPScott]

Yo @eldewen will you be opening up a PR for bring the warnings back?

[stale]

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 30 days. Thanks!

[BPScott]

poke stale bot, I'd still like to see this ticket addressed

[shilman]

@BPScott see #9535
@ndelangen can we close?

[ndelangen]

Yes, I think that resolves this issue.