You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When using storybook in webpack5 mode all errors in the source code will be suppressed down to warning in a console and to feedback is displayed
To Reproduce
webpack4
Start storybook
break a source code (import front file or make a syntax mistake)
an error is shown in the terminal and browser window
the story disappears
webpack5
Start storybook
break a source code (import front file or make a syntax mistake)
no error is shown neither in the terminal, nor browser window
the story (just) disappears
The same is happening during the initial build - the build just failing with no reason provided.
So currently we cannot do a lot. We have to wait for a new webpack-hot-middleware version, which fixes the issue.
I have found a hacky solution by pinning the webpack-hot-middleware version to a commit in a fork of webpack-hot-middleware, described here: webpack-contrib/webpack-hot-middleware#390 (comment) (use it at your own risk) This was working for me. The build error was successfully propagated to the frontend error overlay.
We’re cleaning house! Storybook has changed a lot since this issue was created and we don’t know if it’s still valid. Please open a new issue referencing this one if:
Describe the bug
When using storybook in webpack5 mode all errors in the source code will be suppressed down to warning in a console and to feedback is displayed
To Reproduce
webpack4
webpack5
The same is happening during the initial build - the build just failing with no reason provided.
System
Additional context
Probably
react-error-overlay
never was "really" here (apart of #2900) and was included due to CRA defaults.I've tried to add https://github.com/gregberge/error-overlay-webpack-plugin but is had no effect, probably something more than just plugin is required.
The text was updated successfully, but these errors were encountered: