-
Notifications
You must be signed in to change notification settings - Fork 295
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
Cannot handle css-loader error #334
Comments
Hrm, i thought there was a way to customise the process-update behaviour and the arguments passed to The code was last touched in #254 Is there a way to configure CSS loader to not error in that scenario? |
There is my small mistake, error is emitted by Suddenly there is no way to customize Right now I implement console.error wrapper to handle this error
By I feel a bit uncomfortable with this solution. |
Note: |
@glenjamin To solve this problem the following options should be customizable?
I believe I can make a PR on this weekend for this capabilities. |
I think it might be a bit more complicated than that to get the behaviour correct. I think perhaps the right logic might be to not ignore if reload is true. |
Description
I use
css-loader
with enabledmodules
option.When I add any new css rule
css-loader
throw error:In that case I want to reload page, but
webpack-hot-widdleware
ignores any errors and I'm not able to handle errors and reload page.Reproduction
https://github.com/AndreasCag/hot-reload-bug-repro
How Do We Reproduce?
npm i
npm run dev
localhost:3000
./src/test.css
and add the following rule at the end of fileActual behaviour
Expected behaviour
Page automatically reloaded
The text was updated successfully, but these errors were encountered: