-
Notifications
You must be signed in to change notification settings - Fork 27k
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 -- can't find hot-update.json. #4310
Comments
Additonal information: I have done some more clean up, but am still encountering the error in this issue. I was just on NO files had changed but it reports all of the imported files as having changed. I know that having |
I think this might also be related to #4232 I have tried declaring my components every possible way I can think of, using classes, functions, fat arrow exports, wrapping in connect, exporting a component that has the connected component, no luck. |
Without a minimal reproduction it's impossible for me to look into this. |
I can appreciate that you need something to reproduce this with. However, I have been banging away at this for about a week and haven't been able to figure out how to create a reproducible example since the app this is coming from is large. Would we be able to potentially setup a video call / pair session so that I can give you access to the project? I can't give you the source directly, since it is our main application. |
I'm also running into a chunk not finding the hot-reload.json file but it doesn't seem to be written to the filesystem which would explain the 404. However looking at the page's js, it is referencing the file and has the hash |
@Kyle-Mendes We're you ever able to figure this out? I have basically the same setup (using next-sass and |
Will probably be fixed in |
I tried to create a repro app, but it didn’t have the same issue. I’m also running this through docker, which is making me think that might be the root cause. |
@timneutkens Update: tried with canary, still same result. My guess its something to do with integrating to my the existing express app, but can't quite figure out the issue. After some more digging, I found that eventually the I'm not too familiar with how |
Have the same issue. The updates are always one step behind. Did anyone figure something out? |
I have the same issue, any idea? |
Faced also. Next is getting annoying. It is not working out of the box as expected. |
Please create a new issue that provides a clear and concise reproduction so that we can investigate. |
This seems to be an OS-dependent issue, we have a large project that works fine on 5 systems and fails similarly on one. I tried to pin down the differences between that system and the others and so far no luck:
Still one system has 404 at HMR and others don't. |
my guess would be that some of the environment variables are of significance, here's a
|
Expected Behavior
using:
zeit/next-sass
for mynext.config.js
server.js
with a custom directoryconst application = next({ dev, dir: './src' });
I have just updated to next 6.0.0 and I can't use my site because the HMR fails to find any information, causing any route requests to result in a full reload.
The site works when loaded with
yarn build && yarn start
Folder structures:
EDIT:
It seems like the files are supposed to go directly into
.next
I see that happening in a small test repo that I made. However, it now seems that if that's the case, the error I'm encountering is actually the fact that the HMR is unable to find thehot-update.json
files when updates are made.END EDIT
When on page
/apps/Public/sign_in
as/sign_in
I click on<Link to="/apps/Public/forgot_password" as="forgot_password" />
Result:
Initial page loads of all pages works perfectly. However, any route changes fail.
Debugging
I have tried just about everything I can think of. It seems like this error is caused from my
./src/.next
file not having a/webpack
directory. My understanding is that HMR will look for thehot-update.json
files in/webpack
However, in my case, all
hot-update.json
files are in./src/.next
Contents of
./src/.next
Questions:
/webpack
directory?Your Environment
The text was updated successfully, but these errors were encountered: