-
Notifications
You must be signed in to change notification settings - Fork 54
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
reload #79
Comments
@rmsheppard try to set |
I'm not entirely sure the caching functionality is working as expected. Subsequent executions seem to result in the output of EDIT: I see this is tracked in #45 |
I've set |
It's been a while since the last post, but I've got the same issue, and I think I might have an idea. I'm using module.scss files btw, but it should be the same. The reason that webpack watch doesn't get re-triggered seems to be that webpack doesn't know about the scss file. Babel effectively strips out the scss file and replaces it with the inline class references, and webpack doesn't even parse the scss file. As far as webpack knows, these files do not exist. I'm thinking...
If anyone knows how to do any of the above, that might help me. Some context. I'm making an express MVC app that uses React as a view-engine with no client side javascript at all. I still want Sass modules, as it makes managing code easier. |
I have this set up and working in my project. However, it only is able to execute on initial compile. Is there any way to run this upon hot module reload?
The text was updated successfully, but these errors were encountered: