AI & Agent Dev Bug Sandbox Back to Radar

Metadata Routes With `Export Const Revalidate` Are Emitted As Static Files In Adapter Output, Dropping Revalidate On Vercel

sitemap.ts (and robots.ts) that export `revalidate` are incorrectly classified as STATIC_FILE in the adapter build output, losing their revalidate value and causing stale content on Vercel. The route is never regenerated and no function is emitted.

highConfidence 85%Next.js Affected V16.2.0 Affected V16.2.11 Affected V16.3.3 Affected V16.3.5 Affected V16.4.0-Canary.38

Origin Analysis

In `packages/next/src/build/adapter/build-complete.ts`, metadata routes matching `isStaticMetadataFile(route)` are unconditionally added to `staticFiles` as STATIC_FILE when a `.body` file exists, and the app routes loop skips them. Neither path checks `prerenderManifest.routes[route].initialRevalidateSeconds`, so the revalidate configuration is ignored.

1. Create a Next.js project with `app/sitemap.ts` exporting `revalidate = 10` and `app/feed.xml/route.ts` exporting `revalidate = 10`. 2. Run `npm install && npm run build` with an adapter enabled (`NEXT_ENABLE_ADAPTER=1` or `adapterPath`). 3. Inspect the adapter's `onBuildComplete` output: `/sitemap.xml` appears as `{type:'STATIC_FILE'}` while `/feed.xml` appears as `{type:'PRERENDER', initialRevalidate:10}`. 4. Deploy to Vercel; `/sitemap.xml` is served from `.vercel/output/static/` and does not revalidate, showing stale content.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

This change only affects adapter builds. It does not handle `revalidate = 0` (which should likely be dynamic rather than static) because the condition uses `> 0`; such routes would still be treated as static. If dynamic behavior is required for `revalidate = 0`, additional logic is needed. Rollback: revert this patch or use the workaround `await connection()` in metadata routes. Test on Vercel and with `next start` to ensure parity, especially for metadata routes that share paths with custom route handlers.