-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
[HMR] Update check failed #813
Comments
Have you tried rebuild? |
@Piterden Closing this. I fixed it by replacing the files in my build and config folders with the ones in the template repo. Something must have gotten messed up along my development path. |
@Piterden Okay that didnt actually work. Looks like the problem is intermittent. What did you mean by rebuild? |
I'm having the same issue. |
@Piterden |
This #751 (comment) fixed the issue for me too. |
@piehei Hey so thanks for finding that comment, that works for me too. I didnt realize webpack 3 was out, so when I ran npm-check-updates I upgraded. Still curious about why we dont need those lines of code anymore |
What you solved this question? [HMR] Update failed: Error: Manifest request to 169319f72cbe014b6608.hot-update.json failed. |
@HauntedSmores What you solved this question? [HMR] Update failed: Error: Manifest request to 169319f72cbe014b6608.hot-update.json failed. |
[HMR] Update check failed: Error: Manifest request to /0ca55ad0f6c9c867e01c.hot-update.json timed out. at XMLHttpRequest.request.onreadystatechange (http://localhost:8080/app.js:39:22)
From what I can tell, this happened after running
npm update
. From looking at other github issues such as this one: webpack/webpack-dev-middleware#68it seems like its an issue with the path config in webpack but this templates webpack config is almost too modularized so its hard to trace where its being set from.
EDIT: Found where the output path for the middleware is being set and traced the variable and it seems to be set properly. I also tried replacing my build and config folders with fresh ones from the repo. Still getting the issue.
The text was updated successfully, but these errors were encountered: