vercel/next.js · error · WrappedBuildError
missing required error components
Error message
missing required error components
What it means
Dev-mode failure in base-server's rendering path: the error boundary components (global-error/error page) that must wrap every render have not been compiled yet by the hot dev server. The server first serves a minimal HTML page that polls the URL and reloads once compilation finishes, then throws this WrappedBuildError to surface the incomplete compilation state.
Source
Thrown at packages/next/src/server/base-server.ts:3347
<pre>missing required error components, refreshing...</pre>
<script>
async function check() {
const res = await fetch(location.href).catch(() => ({}))
if (res.status === 200) {
location.reload()
} else {
setTimeout(check, 1000)
}
}
check()
</script>`,
HTML_CONTENT_TYPE_HEADER
),
}
}
throw new WrappedBuildError(
new Error('missing required error components')
)
}
// If the page has a route module, use it for the new match. If it doesn't
// have a route module, remove the match.
if (result.components.routeModule) {
addRequestMeta(ctx.req, 'match', {
definition: result.components.routeModule.definition,
params: undefined,
})
} else {
removeRequestMeta(ctx.req, 'match')
}
try {
return await this.renderToResponseWithComponents(
{View on GitHub (pinned to 258b1c1bc0)
Solutions
- Rebuild the application; required error components (error.js / global-error.js / not-found) are missing from the build output.
Defensive patterns
Strategy: fallback
When it happens
Trigger: The server cannot load the required error components for a build.
Common situations: A corrupted or mismatched .next build is missing compiled error component entries.
AI-assisted analysis of vercel/next.js@258b1c1bc0 (2026-08-19).
Data as JSON: /api/errors/6044612c2b7febf2.
Report an issue: GitHub.