vercel/next.js · error · ExportError
Export encountered errors on ${failedPages.length} ${failedP
Error message
Export encountered errors on ${failedPages.length} ${failedPages.length === 1 ? 'path' : 'paths'}:
${failedPages.sort().join('\n\t')} What it means
Final failure report in exportAppImpl: the export run collected failedExportAttemptsByPage entries — pages whose prerender/export attempts threw. It aggregates the failed pages, sorts them, and lists them (tab-indented) under this summary as the terminating error so the user sees exactly which paths did not export.
Source
Thrown at packages/next/src/export/index.ts:1054
'/' + segmentFileSrc.slice(0, -RSC_SEGMENT_SUFFIX.length)
const segmentFilename =
convertSegmentPathToStaticExportFilename(segmentPath)
const segmentFileDest = join(segmentsDirDest, segmentFilename)
await fs.mkdir(dirname(segmentFileDest), { recursive: true })
await fs.copyFile(
join(segmentsDir, segmentFileSrc),
segmentFileDest
)
})
)
}
})
)
}
if (failedExportAttemptsByPage.size > 0) {
const failedPages = Array.from(failedExportAttemptsByPage.keys())
throw new ExportError(
`Export encountered errors on ${failedPages.length} ${failedPages.length === 1 ? 'path' : 'paths'}:\n\t${failedPages
.sort()
.join('\n\t')}`
)
}
await fs.writeFile(
join(distDir, EXPORT_DETAIL),
formatManifest({
version: 1,
outDirectory: outDir,
success: true,
}),
'utf8'
)
if (telemetry) {
await telemetry.flush()View on GitHub (pinned to 258b1c1bc0)
Solutions
- Fix the errors on the listed paths (see earlier build output) and re-run the export.
Defensive patterns
Strategy: validation
When it happens
Trigger: Static export fails to prerender one or more pages.
Common situations: A page throws during prerendering when building with output: export.
AI-assisted analysis of vercel/next.js@258b1c1bc0 (2026-08-19).
Data as JSON: /api/errors/214e0cc50bce61a0.
Report an issue: GitHub.