Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix next.js 16 lacks build size info [3 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

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#85712•Fetched 2026-04-08 02:14:13
View on GitHub
Comments
3
Participants
3
Timeline
9
Reactions
0
Author
gengjiawengengjiawen
Participants
gengjiawengengjiawengithub-actions[bot]github-actions[bot]mischnicmischnic
Timeline (top)
commented ×3labeled ×2closed ×1issue_type_added ×1

Code Example

Operating System:
  Platform: linux
  Arch: x64
  Version: #71-Ubuntu SMP PREEMPT_DYNAMIC Tue Jul 22 16:52:38 UTC 2025
  Available memory (MB): 7752
  Available CPU cores: 4
Binaries:
  Node: 22.21.1
  npm: 10.9.4
  Yarn: 1.22.22
  pnpm: 9.15.9
Relevant Packages:
  next: 16.0.1 // Latest available version is detected (16.0.1).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: N/A
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/gengjiawen/repro-nextjs

To Reproduce

create a new next 16 project and build

Current vs. Expected behavior

current: no build info

Route (app) ┌ ƒ / ├ ○ /_not-found ├ ƒ /api/hetzner-traffic

on nextjs 15:

Route (app) Size First Load JS
┌ ƒ / 3.46 kB 105 kB ├ ○ /_not-found 991 B 102 kB ├ ƒ /api/hetzner-traffic 133 B 101 kB

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #71-Ubuntu SMP PREEMPT_DYNAMIC Tue Jul 22 16:52:38 UTC 2025
  Available memory (MB): 7752
  Available CPU cores: 4
Binaries:
  Node: 22.21.1
  npm: 10.9.4
  Yarn: 1.22.22
  pnpm: 9.15.9
Relevant Packages:
  next: 16.0.1 // Latest available version is detected (16.0.1).
  eslint-config-next: N/A
  react: 19.2.0
  react-dom: 19.2.0
  typescript: N/A
Next.js Config:
  output: N/A

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

Turbopack

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

next build (local)

Additional context

No response

extent analysis

TL;DR

The issue with missing build info in Next.js 16 can be addressed by investigating the differences in build output between Next.js 15 and 16, potentially involving changes in Turbopack configuration.

Guidance

  • Review the Next.js 16 documentation and release notes to identify any changes in build output or Turbopack configuration that may be causing the missing build info.
  • Compare the next.config.js files between the Next.js 15 and 16 projects to identify any differences in configuration that may be contributing to the issue.
  • Check the Turbopack configuration options to see if there are any settings that can be adjusted to include build info in the output.
  • Investigate the possibility of a bug in Next.js 16 or Turbopack that is causing the missing build info, and consider opening an issue on the Next.js GitHub repository if necessary.

Example

No code snippet is provided as the issue does not include sufficient information to create a specific example.

Notes

The issue may be specific to the combination of Next.js 16 and Turbopack, and may require further investigation to determine the root cause.

Recommendation

Apply workaround: The best course of action is to investigate the differences in build output between Next.js 15 and 16, and adjust the Turbopack configuration as needed to include build info in the output.

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…
#api#retrieval issue#search optimization#API routing#API middleware

Still need to ship something?

×6

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

Back to top recommendations

TRENDING