New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parallel routes: remove the per-route default 404 handler #48286
Conversation
Failing test suitesCommit: 2ce8697
Expand output● Document and App › Rendering via HTTP › _document › It adds nonces to all scripts and preload links
Read more about building and testing Next.js in contributing.md.
Expand output● ReactRefreshLogBox default › Module not found (missing global CSS)
Read more about building and testing Next.js in contributing.md.
Expand output● app dir - navigation › redirect › components › should redirect to external url
● app dir - navigation › redirect › next.config.js redirects › should redirect from next.config.js
Read more about building and testing Next.js in contributing.md. |
This PR fixes an issue where throwing a notFound error in a parallel route at the top level at the root level would trigger a notfound boundary at the parallel route level, which meant in practice that you could still see the other slots being rendered below.
This behaviour is undesirable and was caused by the fact that we were inserting a default one at each top-level parallel route. This is not longer needed as we have a global one in
app-router.tsx
fixes NEXT-968