nextjs - 💡(How to fix) Fix Bug Report: Next.js 16.2.1 hangs indefinitely on dev and build with no error output [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#92138Fetched 2026-04-08 01:56:51
View on GitHub
Comments
1
Participants
2
Timeline
5
Reactions
0
Author
Timeline (top)
closed ×1commented ×1issue_type_added ×1labeled ×1

Error Message

Bug Report: Next.js 16.2.1 hangs indefinitely on dev and build with no error output

[HANGS HERE - no further output, no error, no response] [HANGS HERE - no further output, no error, process never completes]

  • No error messages are displayed
  • If there's an issue, an error message should be displayed
  • The hang occurs silently without any error output

Code Example

> next dev

Next.js 16.2.1 (Turbopack)
- Local:         http://localhost:3000
- Environments: .env
- Experiments (use with caution):
  ✓ mdxRs
  · optimizePackageImports
  ⨯ serverSourceMaps
  ✓ turbopackFileSystemCacheForBuild
  ✓ webpackMemoryOptimizations

Starting...
Ready in xxxxms
Compiling /[locale]/ 

[HANGS HERE - no further output, no error, no response]

---

> next build

Next.js 16.2.1 (Turbopack)
- Environments: .env
- Experiments (use with caution):
  ✓ mdxRs
  · optimizePackageImports
  ⨯ serverSourceMaps
  ✓ turbopackFileSystemCacheForBuild
  ✓ webpackMemoryOptimizations

Creating an optimized production build ...

[HANGS HERE - no further output, no error, process never completes]

---

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32510
  Available CPU cores: 20
Binaries:
  Node: 24.14.0
  npm: 10.5.2
  pnpm: 10.33.0
Relevant Packages:
  next: 16.2.1
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/vercel/next.js/issues

To Reproduce

Bug Report: Next.js 16.2.1 hangs indefinitely on dev and build with no error output

Link to the code that reproduces this issue

Private repository: large-scale Next.js application with 32 locales, 100+ pages, MDX content

To Reproduce

  1. Upgrade from Next.js 16.1.7 to 16.2.1
  2. Run pnpm dev or pnpm build
  3. Observe the process hangs indefinitely with no progress

Dev output:

> next dev

▲ Next.js 16.2.1 (Turbopack)
- Local:         http://localhost:3000
- Environments: .env
- Experiments (use with caution):
  ✓ mdxRs
  · optimizePackageImports
  ⨯ serverSourceMaps
  ✓ turbopackFileSystemCacheForBuild
  ✓ webpackMemoryOptimizations

✓ Starting...
✓ Ready in xxxxms
○ Compiling /[locale]/ 

[HANGS HERE - no further output, no error, no response]

Build output:

> next build

▲ Next.js 16.2.1 (Turbopack)
- Environments: .env
- Experiments (use with caution):
  ✓ mdxRs
  · optimizePackageImports
  ⨯ serverSourceMaps
  ✓ turbopackFileSystemCacheForBuild
  ✓ webpackMemoryOptimizations

Creating an optimized production build ...

[HANGS HERE - no further output, no error, process never completes]

Current vs. Expected behavior

Current vs. Expected behavior

Current behavior:

  • Both next dev and next build hang indefinitely after initial startup
  • No error messages are displayed
  • No warnings or hints about what's causing the hang
  • Process must be manually terminated (Ctrl+C)
  • No CPU activity observed after the initial compilation starts

Expected behavior:

  • Dev server should compile and serve pages normally
  • Build should complete successfully
  • If there's an issue, an error message should be displayed

Which area(s) are affected?

  • React
  • Turbopack
  • App Router

Which stage(s) are affected?

  • next dev (local)
  • next build (local)

Additional context

Working version: Next.js 16.1.7 with React 19.2.4 - works perfectly

Broken version: Next.js 16.2.1 with React 19.2.4 - hangs indefinitely

Project characteristics:

  • Large-scale application with 32 locale support (next-intl)
  • 100+ pages including games, psychological tests, tools
  • MDX content for docs and blog
  • DaisyUI + Tailwind CSS

Notes:

  • The hang occurs silently without any error output
  • No verbose mode or debug flag seems to provide more information
  • This is a regression from 16.1.7 to 16.2.1
  • Both dev and build are affected

Provide environment information

Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32510
  Available CPU cores: 20
Binaries:
  Node: 24.14.0
  npm: 10.5.2
  pnpm: 10.33.0
Relevant Packages:
  next: 16.2.1
  react: 19.2.4
  react-dom: 19.2.4
  typescript: 5.9.3
Next.js Config:
  output: N/A

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

Not sure

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

next build (local)

Additional context

No response

extent analysis

TL;DR

Downgrade to Next.js 16.1.7 to resolve the indefinite hang issue in both next dev and next build commands.

Guidance

  • Verify that the issue is specific to Next.js 16.2.1 by checking if the problem persists across different environments and Node versions.
  • Attempt to isolate the issue by creating a minimal reproducible example to identify if any specific features (e.g., MDX content, locale support) are contributing to the hang.
  • Consider opening an issue on the Next.js GitHub repository, providing detailed steps to reproduce the problem, as this appears to be a regression from version 16.1.7.
  • If possible, try enabling verbose mode or debug flags to gather more information about the hang, although the issue report suggests this may not yield additional insights.

Example

No specific code snippet can be provided without more context on the exact cause of the hang, but creating a minimal example to reproduce the issue would be a crucial step in debugging.

Notes

The hang seems to be a regression introduced in Next.js 16.2.1, given that version 16.1.7 works as expected. The large scale of the application and the use of specific features like MDX content and locale support might be contributing factors, but without further investigation, it's challenging to pinpoint the exact cause.

Recommendation

Apply workaround: Downgrade to Next.js 16.1.7, as it is known to work correctly, until a fix for the regression in 16.2.1 is available. This recommendation is based on the information provided that 16.1.7 works perfectly, and the issue is introduced in 16.2.1.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

nextjs - 💡(How to fix) Fix Bug Report: Next.js 16.2.1 hangs indefinitely on dev and build with no error output [1 comments, 2 participants]