HMR -- can't find hot-update.json.

[Kyle-Mendes]

• I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior

using:

• zeit/next-sass for my next.config.js
• a custom server.js with a custom directory
  • const application = next({ dev, dir: './src' });
• Flow js for type checking
• Redux and Apollo

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:

./src
  /pages
    /apps
      /Public
        index.js
        sign_in.js
        sign_up.js
        forgot_password.js
      /Admin
        .......

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 the hot-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 the hot-update.json files in /webpack

However, in my case, all hot-update.json files are in ./src/.next

Contents of ./src/.next

Questions:

• Why do I not have a /webpack directory?
• I can't create a reproduction repo, can someone from Zeit help by looking through my private repo?

Your Environment

Tech	Version
next	6.0
node	9.11.1
OS	Mac OS
browser	Chrome

[Kyle-Mendes]

Additonal information:

I have done some more clean up, but am still encountering the error in this issue. I was just on forgot_password and tried to route to sign_up

NO files had changed but it reports all of the imported files as having changed.

I know that having component in pages is an anti-pattern. I'm in the process of removing those.

[Kyle-Mendes]

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.

[timneutkens]

Without a minimal reproduction it's impossible for me to look into this.

[Kyle-Mendes]

@timneutkens

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.

[stramel]

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

[kochis]

@Kyle-Mendes We're you ever able to figure this out? I have basically the same setup (using next-sass and dir), and am seeing the exact same issue.

[timneutkens]

Will probably be fixed in next@canary but I'm not sure since I still don't have a reproduction.

[kochis]

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.

[kochis]

@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 hot-update file does get written to disk, but only after something causes a change (building a new page, or old page is disposed). It seems like the hot-update.json files on disk are always one step behind the file being requested from the client.

I'm not too familiar with how webpack-dev-middleware works, but are the files supposed to be on disk before they can be served, or does the middleware serve them from memory? Trying to figure if maybe something is preventing them from being written to the disk at the right time.

[eivindml]

Have the same issue. The updates are always one step behind.

Did anyone figure something out?

[MoctezumaDev]

I have the same issue, any idea?

[marklalata]

Faced also. Next is getting annoying. It is not working out of the box as expected.