Hot reload not working at latest version of Next.js

[jarvislin94]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.5.0: Mon Apr 24 20:53:44 PDT 2023; root:xnu-8796.121.2~5/RELEASE_ARM64_T8103
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: 8.5.1
    Relevant packages:
      next: 13.4.5-canary.12
      eslint-config-next: 13.4.5
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

To Reproduce

1. npx create-next-app@latest (next-tw)
2. yarn install
3. yarn dev

Describe the Bug

main-app.js:1425 Uncaught TypeError: __webpack_require__.ts is not a function
    at (app-client)/./node_modules/next/dist/compiled/@next/react-refresh-utils/dist/runtime.js

Expected Behavior

Hot reload should work

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[kelvinsekx]

I am facing the same problem with the next blog example template: npx create-next-app --example blog my-blog

Even when I downgrade my next version to 13.4.0v, it still doesn't work. I am using exactly what the template gave me without making any changes.

So I can image the kind of frustrations others who might have used this must have faced.

Here is my package and folder tree

[JasonA-work]

@leerob

Would you mind taking a look at this please? It's really killing dev productivity...(and is very frustrating since we've been spoiled with a super awesome HMR prior to this)

Would appreciate it so much!

[kelvinsekx]

So I got a fix for mine. I think the hot reload works.
If you are working with WSL2 on Windows, ensure you move your next folders or app to the home <your_name>:/home$ directory.

In fact, it has nothing to do with NextJs in my case. The next app was in the mnt/c <your_name>:/mnt/c$ folders was what made the HMR not work.

[JasonA-work]

I'm glad you found a solution for yours.

I'm not using wsl2 but mine performs full reload for almost every change. Even file saves without any changes causes a full reload.

[s-fletcher]

I was unable to reproduce using your steps. However, I am having this issue with my own project which started in v13.3.0. I was able to narrow it down to an issue around the custom server. Removing this server resolved my issue.

Looks like custom servers also impact some other performance optimizations (see below from the documentation).

Good to know:

• Before deciding to use a custom server, please keep in mind that it should only be used when the integrated router of Next.js can't meet your app requirements. A custom server will remove important performance optimizations, like serverless functions and Automatic Static Optimization.
• A custom server cannot be deployed on Vercel.

I'll be working on my own workaround without a custom server.

Hopefully this helps!

[eashish93]

Yes custom server is the problem hot reload not working with latest next.js version. But it's a requirement as middleware doesn't support node runtime.

[jd-carroll]

If anyone is using a custom server for https support only, take a look at #53926

Looking for any kind of feedback

[weyert]

Looks like its working in canary build? The 13.4.14-canary.5 versions seems to solve my issues regarding not compiling or detecting file changes.

[meds]

@weyert not working for me as of 13.4.19

[McAndersC]

Testing not-found.js on a fresh build also just returns a blank page. Everything worked in 13.4.2 when I test it.

[McAndersC]

4 days. Is it just me but the current npx create-next-app@latest is broken. It does not refresh on editing and a simple not-found leaves a blank page. Can someone please confirm that this is true. before i loose my marbles.

This is straight out the box, no custom servers - no nothing?

[leerob]

Could everyone please provide their environment info similar to the original issue? And what is the last version it is working for you?