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
{{ message }}
This repository was archived by the owner on Apr 8, 2020. It is now read-only.
This will result in the following server-side exception:
fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[0]
An unhandled exception has occurred: Call to Node module failed with error: Error: The location '/__webpack_hmr' doesn't match any route configured in react-router.
at ClientApp\boot-server.js:1:802
How can I prevent this? Why is Webpack Hot Module Replacement kicking off in production mode - at least server-side?
The text was updated successfully, but these errors were encountered:
I think you just have some other development-mode browser tab still running that's trying to connect to /__webpack_hmr. So it's nothing to do with your production app :)
If this turns out to be wrong and you can confirm the issue is something else, please reopen with details.
Steps to reproduce, following http://blog.stevensanderson.com/2016/05/02/angular2-react-knockout-apps-on-aspnet-core/
yo aspnetcore-spa
(using version 0.3.4)set ASPNETCORE_ENVIRONMENT=Production
webpack --config webpack.config.vendor.js
webpack
dotnet run
This will result in the following server-side exception:
How can I prevent this? Why is Webpack Hot Module Replacement kicking off in production mode - at least server-side?
The text was updated successfully, but these errors were encountered: