vercel / vercel/next.js

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

Open
#61,995 31 comments 10 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Lazy Loading Linking and Navigating Module Resolution Pages Router Runtime
Dominant language
JavaScript
Stars
142k
Forks
32.4k
Avg merge
2d 14h
Merged PRs (30d)
351

Description

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.

_

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked dashawk/nextjs-14-bugger reproduction, run yarn install && yarn dev, and browse to localhost:3000 using the reported Next.js 14.1.0 environment. Compare the behavior with the referenced canary fix and trace the failing development path; done means the reproduction loads without the reported TypeError.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, next.js, react
Domain
frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.