-
Notifications
You must be signed in to change notification settings - Fork 23
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
react-transform-catch-errors and webpack-dev-server #17
Comments
Ended up just using webpack-dev-middleware and webpack-hot-middleware with react-transform-catch-errors and redbox-react. Works perfectly. |
It should work with WebpackDevServer just fine. React Transform doesn't care what you use to connect to dev server. The fact that we use it with the middleware in the examples is just a coincidence. However we can't help you if you don't post a full project reproducing the issue. |
Please provide a way to reproduce. |
I am also seeing this behavior. If I run
|
@craigjennings11 This transform just catches runtime errors. What you show is a syntax error. It is unrelated to this transform. |
Hmm, I may not be explaining it properly. While the server is running, I switch those lines and save the file. This causes a full refresh and console error. When I watch the demo gif here, there is a point where the text changes from |
Note that I can also reproduce this with https://github.com/rackt/redux/tree/master/examples/counter by running |
What you want is unrelated to this transform. Syntax error overlay is a feature of a different project called webpack-hot-middleware. It's a replacement for webpack-dev-server. |
Gotcha, thanks for the help |
Currently trying to get react-transform-catch-errors to work with redbox-react while still using webpack-dev-server. I was able to get the react-transform-hmr to work with webpack-dev-server but am still not able to set it up with react-transform-catch-errors. Is this possible or does it have to be set up with webpack-hot-middleware (and express)?
The text was updated successfully, but these errors were encountered: