vercel/next.js

Dev server stuck on state - "Cannot read properties of null (reading 'useContext')"

AlonMiz opened this issue · 1 comments

AlonMiz commented

Link to the code that reproduces this issue

not yet

To Reproduce

  1. Start the app, all works well
  2. change some files, maybe even save an invalid ts syntax
  3. turbopack stuck in a state where it cannot recover until restarting the dev server

Current vs. Expected behavior

Current behavior

Occasionally turbopack reaches a point of no return. the bundler cannot recover from the invalid state although, in some sense, nothing has changed.
The only thing that helps it is to restart the dev server

Expected behavior

I would expect that a bad syntax would fail, but when fixing it the bundler should recover

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:10:42 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 8
Binaries:
  Node: 21.7.3
  npm: 10.5.0
  Yarn: 1.22.18
  pnpm: 8.5.0
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A

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

Runtime, Turbopack, TypeScript

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

next dev (local)

Additional context

GET /settings/card-types 500 in 360ms
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
 ⨯ TypeError: Cannot read properties of null (reading 'useContext')
    at usePathname (/.next/server/chunks/ssr/node_modules_next_dist_esm_1c713e._.js:3826:238)
    at ErrorBoundary (/.next/server/chunks/ssr/node_modules_next_dist_esm_1c713e._.js:4136:227)
digest: "1457145659"
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
TypeError: Cannot read properties of null (reading 'useContext')
    at t.useContext (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:162241)
    at usePathname (/.next/server/chunks/ssr/node_modules_next_dist_esm_1c713e._.js:3826:238)
    at ErrorBoundary (/.next/server/chunks/ssr/node_modules_next_dist_esm_1c713e._.js:4136:227)
    at au (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:10446)
    at /node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:15122
    at aw (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
    at a_ (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:49776)
    at ab (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:11808)
    at /node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16871
    at aw (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
    at aw (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:46505)
    at a_ (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:49776)
    at ab (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:11808)
    at /node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16871
    at aw (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:16908)
    at a_ (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:49776)
    at /node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:58612
    at /node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:59270
    at aN (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:59278)
    at Timeout._onTimeout (/node_modules/next/dist/compiled/next-server/app-page.runtime.dev.js:35:6939)
    at listOnTimeout (node:internal/timers:573:17)
    at process.processTimers (node:internal/timers:514:7)
github-actions commented

We could not detect a valid reproduction link. Make sure to follow the bug report template carefully.

Why was this issue closed?

To be able to investigate, we need access to a reproduction to identify what triggered the issue. We need a link to a public GitHub repository (template for App Router, template for Pages Router), but you can also use these templates: CodeSandbox: App Router or CodeSandbox: Pages Router.

The bug template that you filled out has a section called "Link to the code that reproduces this issue", which is where you should provide the link to the reproduction.

  • If you did not provide a link or the link you provided is not valid, we will close the issue.
  • If you provide a link to a private repository, we will close the issue.
  • If you provide a link to a repository but not in the correct section, we will close the issue.

What should I do?

Depending on the reason the issue was closed, you can do the following:

  • If you did not provide a link, please open a new issue with a link to a reproduction.
  • If you provided a link to a private repository, please open a new issue with a link to a public repository.
  • If you provided a link to a repository but not in the correct section, please open a new issue with a link to a reproduction in the correct section.

In general, assume that we should not go through a lengthy onboarding process at your company code only to be able to verify an issue.

My repository is private and cannot make it public

In most cases, a private repo will not be a sufficient minimal reproduction, as this codebase might contain a lot of unrelated parts that would make our investigation take longer. Please do not make it public. Instead, create a new repository using the templates above, adding the relevant code to reproduce the issue. Common things to look out for:

  • Remove any code that is not related to the issue. (pages, API routes, components, etc.)
  • Remove any dependencies that are not related to the issue.
  • Remove any third-party service that would require us to sign up for an account to reproduce the issue.
  • Remove any environment variables that are not related to the issue.
  • Remove private packages that we do not have access to.
  • If the issue is not related to a monorepo specifically, try to reproduce the issue without a complex monorepo setup

I did not open this issue, but it is relevant to me, what can I do to help?

Anyone experiencing the same issue is welcome to provide a minimal reproduction following the above steps by opening a new issue.

I think my reproduction is good enough, why aren't you looking into it quickly?

We look into every Next.js issue and constantly monitor open issues for new comments.

However, sometimes we might miss one or two due to the popularity/high traffic of the repository. We apologize, and kindly ask you to refrain from tagging core maintainers, as that will usually not result in increased priority.

Upvoting issues to show your interest will help us prioritize and address them as quickly as possible. That said, every issue is important to us, and if an issue gets closed by accident, we encourage you to open a new one linking to the old issue and we will look into it.

Useful Resources