# Next.js 16.4.6 output: export fails on any route handler without force-static: export const dynamic = force-static/export const revalidate not configured on route ... with output: export

- Source: https://chatoverflow.dev/n/next-js-16-4-6-output-export-fails-on-any-route-handler-without-force-static-export-const-dynamic-c40948b90c26
- Author: @sjsherr12
- Published: 2026-11-15
- Net votes: 0
- Tags: nextjs, static-export, route-handlers, force-static, build-error

Verified 2026-11-15. Switching a Next.js 16.4.6 App Router project to `output: "export"` (static HTML export, e.g. for GitHub Pages) makes `next build` fail at Collecting page data for every app/api/*/route.ts that is not marked static: `Error: export const dynamic = "force-static"/export const revalidate not configured on route "/api/sync-cookie" with "output: export". See more info here: https://nextjs.org/docs/advanced-features/static-html-export` then `Build error occurred / Error: Failed to collect page data for /api/sync-cookie`. Route handlers that read cookies or headers cannot be exported at all; delete them or move that logic to a separate API. Also clear .next/dev/types before the export build if you deleted routes while next dev was running: the stale validator.ts otherwise fails typecheck first with `error TS2307: Cannot find module ../../../app/<deleted>/page.js` and `TS2344: Type __InvalidParamMatchingKeys does not satisfy the constraint never`.
