next.js: [NextJS 14.1.0] TypeError: Cannot read properties of undefined (reading 'call')

Link to the code that reproduces this issue

https://github.com/dashawk/nextjs-14-bugger

To Reproduce

Current vs. Expected behavior

After doing all the reproduction steps, you will see the error. As you can see, I have already applied the suggested fix for canary@14.1.1-canary.51 image

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
Binaries:
  Node: 20.11.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

App Router, Data fetching (gS(S)P, getInitialProps), Dynamic imports (next/dynamic), Metadata (metadata, generateMetadata, next/head), Middleware / Edge (API routes, runtime), Module resolution (CJS / ESM, module resolving), Routing (next/router, next/navigation, next/link)

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I have encountered this issue only in NextJS@14.1.0 which is giving me a headache.

_

Upgrading might not be a very good habit.

_

About this issue

  • Original URL
  • State: open
  • Created 3 years ago
  • Reactions: 9
  • Comments: 30 (9 by maintainers)

Most upvoted comments

facing the same issue during HMR and navigation when using npm run dev doing ctrl+shift+r (hard reload) removes the error and renders the page correctly but again when a file is changed and HMR is triggered resulting in the same error. using node lts : 20.11.1

Having same issue with NextJS `` “next”: “15.2.4”```

ok when I killed npm run dev and reloaded the localhost the page was still rendered. From the network tab, I got to know the page was being fetched from a service worker so I unregistered it and the problem is gone

Having this a lot in production as well, 14.2.3, node 20.

Cannot read properties of undefined (reading 'call')

Chrome 126.0.0 Windows >=10

Server action to login in a user, basic form that takes email and password

Here is what I did just now.

I still use the node version v20.11.0

Step I did try

# Clean up the cache
npm cache clean --force

# Delete yarn.lock
rm yarn.lock

# Run dev again
yarn dev

I did not see the TypeError anymore. For some reason it fixes the issue. I cannot determine what caused the issue though.