Files
JJ KasperandGitHub c9e5069ee1 Fix i18n fallback: false collision (#82136)
This fixes a case with i18n in pages router with deeply nested mixed
`fallback: false` and `fallback: 'blocking'` routes where the internal
`NoFallbackError` would be bubbled outside of the server handler causing
the invariant to leak instead of rendering the 404 page like expected.

Verified against our E2E deploy tests here
https://github.com/vercel/vercel/actions/runs/16586881087/job/46913897238
and
https://github.com/vercel/next.js/actions/runs/16586877291/job/46913935296

Closes: NEXT-4655
2025-07-29 08:54:13 -07:00

28 lines
387 B
JavaScript

export default function Page() {
return (
<>
<p>page: /[first]/[second]</p>
</>
)
}
export function getStaticProps({ params }) {
return {
props: {
params,
now: Date.now(),
},
}
}
export function getStaticPaths() {
return {
paths: [
{
params: { first: 'first', second: 'second' },
},
],
fallback: false,
}
}