WhatBrokeToday
FAQ
Today's Trends
mediumInvestigatingNext.jsv16.5.0-canary.46

Next.js --debug-prerender Intermittently Classifies ImageResponse Metadata Route as Dynamic

  1. Investigating(current)
  2. Trending(upcoming)
  3. Workaround available(upcoming)
  4. Resolved(upcoming)

Executive summary

Next.js canary builds intermittently misclassify static ImageResponse metadata routes as dynamic when using `--debug-prerender`, causing inconsistent build outputs on identical builds. Developers using next@canary (such as version 16.5.0-canary.46) are affected.

No verified workaround yet

None of the linked reports describe a mitigation. Follow this incident to hear when one appears.

Official fix
Technical root cause

Under active investigation. No report has identified a root cause yet.

Evidence

1 report · 1 GitHubShow
  1. [1]
    GitHub First report
    `--debug-prerender` intermittently classifies an `ImageResponse` metadata route as dynamic (ƒ/○ flip on identical builds)(opens GitHub issue in a new tab)

    Link to the code that reproduces this issue https://github.com/HamedSadim1/nextjs-og-image-prerender-repro To Reproduce npm install (the repo pins next@canary, currently 16.5.0-canary.46). Repeat a cold build and watch the /opengraph-image line: for i in 1 2 3 4 5 6; do rm -rf .next npx next build --debug-prerender | grep opengraph-image done Check whether .next/server/app/opengraph-image.body was written. Current vs. Expected behavior Expected: a metadata image route that reads no dynamic…

    by HamedSadim1 0upvotes 0comments

Timeline

  1. First report on GitHub issue

    `--debug-prerender` intermittently classifies an `ImageResponse` metadata route as dynamic (ƒ/○ flip on identical builds)

    Source