nextjs - 💡(How to fix) Fix /.next/app-build-manifest.json not found in Next build output [1 comments, 2 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#85774Fetched 2026-04-08 02:14:00
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×2closed ×1commented ×1issue_type_added ×1

Code Example

{
  "pages": {
    "/_not-found/page": [
      "static/chunks/webpack-078f6dfb37dff419.js",
      "static/chunks/6278e809-94fb83306815ddb4.js",
      "static/chunks/489-b658b251d0b5dcb5.js",
      "static/chunks/main-app-258584ecda1b4838.js",
      "static/chunks/app/_not-found/page-b05d9c854f8b2476.js"
    ],
    "/layout": [
      "static/chunks/webpack-078f6dfb37dff419.js",
      "static/chunks/6278e809-94fb83306815ddb4.js",
      "static/chunks/489-b658b251d0b5dcb5.js",
      "static/chunks/main-app-258584ecda1b4838.js",
      "static/chunks/app/layout-d33fe6c9d30c32ba.js"
    ],
    "/page": [
      "static/chunks/webpack-078f6dfb37dff419.js",
      "static/chunks/6278e809-94fb83306815ddb4.js",
      "static/chunks/489-b658b251d0b5dcb5.js",
      "static/chunks/main-app-258584ecda1b4838.js",
      "static/chunks/app/page-d33fe6c9d30c32ba.js"
    ]
  }
}

---

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
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: 5.3.3
Next.js Config:
  output: N/A
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/elegant-bell-3z2cp2

To Reproduce

On Next 16 versions

  1. Build the application
  2. Output does not include .next/app-build-manifest.json

Current vs. Expected behavior

If next version is set to <16 output of .next/app-build-manifest.json is:

{
  "pages": {
    "/_not-found/page": [
      "static/chunks/webpack-078f6dfb37dff419.js",
      "static/chunks/6278e809-94fb83306815ddb4.js",
      "static/chunks/489-b658b251d0b5dcb5.js",
      "static/chunks/main-app-258584ecda1b4838.js",
      "static/chunks/app/_not-found/page-b05d9c854f8b2476.js"
    ],
    "/layout": [
      "static/chunks/webpack-078f6dfb37dff419.js",
      "static/chunks/6278e809-94fb83306815ddb4.js",
      "static/chunks/489-b658b251d0b5dcb5.js",
      "static/chunks/main-app-258584ecda1b4838.js",
      "static/chunks/app/layout-d33fe6c9d30c32ba.js"
    ],
    "/page": [
      "static/chunks/webpack-078f6dfb37dff419.js",
      "static/chunks/6278e809-94fb83306815ddb4.js",
      "static/chunks/489-b658b251d0b5dcb5.js",
      "static/chunks/main-app-258584ecda1b4838.js",
      "static/chunks/app/page-d33fe6c9d30c32ba.js"
    ]
  }
}

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
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: 5.3.3
Next.js Config:
  output: N/A

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

Output

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

next build (local)

Additional context

Output is currently helping track page size changes in CI/CD using modified version of hashicorp/nextjs-bundle-analysis

extent analysis

TL;DR

  • The issue with the missing .next/app-build-manifest.json file in Next 16 versions may be resolved by checking the Next.js configuration and build process.

Guidance

  • Review the Next.js configuration to ensure that the output property is correctly set, as this might affect the generation of the .next/app-build-manifest.json file.
  • Verify that the build process is correctly executed and that there are no errors or warnings that could prevent the generation of the manifest file.
  • Check the documentation for Next 16 to see if there are any changes or updates that might affect the generation of the .next/app-build-manifest.json file.
  • Consider downgrading to a previous version of Next.js to see if the issue persists, which could help identify if the problem is specific to version 16.

Notes

  • The issue seems to be specific to Next 16 versions, so any solution or workaround might need to take into account the changes and updates introduced in this version.
  • The use of a modified version of hashicorp/nextjs-bundle-analysis for tracking page size changes in CI/CD might be affected by the missing .next/app-build-manifest.json file, so any solution should also consider this aspect.

Recommendation

  • Apply workaround: The issue might be related to changes in Next 16, so applying a workaround, such as modifying the build process or using a different method for tracking page size changes, might be necessary until a more permanent solution is found.

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 /.next/app-build-manifest.json not found in Next build output [1 comments, 2 participants]