Skip to content
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

Remove default fallback behavior when route group is missing a default #62370

Conversation

ztanner
Copy link
Member

@ztanner ztanner commented Feb 22, 2024

This test case was added in #59752 but this doesn't seem like the correct behavior.

The original PR was intended to be smart about resolving /default.tsx to a route group default (eg /(foo)/default.tsx) when one wasn't specified. But since the route group is creating a new hierarchy in the tree and defines its own layout, if the route group layout doesn't specify a default, then the not found behavior seems correct.

To fix unexpected not-found behavior in this case, you should specify a default at the same level as the layout where the missing slot(s) might be rendered.

Closes NEXT-2565

Copy link
Member Author

ztanner commented Feb 22, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @ztanner and the rest of your teammates on Graphite Graphite

@ztanner ztanner force-pushed the 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default branch from 6b478d4 to a4c5f8b Compare February 22, 2024 01:59
@ztanner ztanner marked this pull request as ready for review February 22, 2024 02:01
@ijjk
Copy link
Member

ijjk commented Feb 22, 2024

Stats from current PR

Default Build (Increase detected ⚠️)
General
vercel/next.js canary vercel/next.js 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default Change
buildDuration 14.4s 14.5s N/A
buildDurationCached 8s 6.8s N/A
nodeModulesSize 196 MB 196 MB N/A
nextStartRea..uration (ms) 404ms 407ms N/A
Client Bundles (main, webpack)
vercel/next.js canary vercel/next.js 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default Change
1068-HASH.js gzip 30.3 kB 30.3 kB N/A
3f784ff6-HASH.js gzip 53.5 kB 53.5 kB N/A
4944-HASH.js gzip 5.04 kB 5.03 kB N/A
8423.HASH.js gzip 181 B 181 B
framework-HASH.js gzip 45.2 kB 45.2 kB
main-app-HASH.js gzip 242 B 244 B N/A
main-HASH.js gzip 32.2 kB 32.1 kB N/A
webpack-HASH.js gzip 1.7 kB 1.7 kB
Overall change 47.1 kB 47.1 kB
Legacy Client Bundles (polyfills)
vercel/next.js canary vercel/next.js 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default Change
polyfills-HASH.js gzip 31 kB 31 kB
Overall change 31 kB 31 kB
Client Pages
vercel/next.js canary vercel/next.js 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default Change
_app-HASH.js gzip 196 B 196 B
_error-HASH.js gzip 184 B 183 B N/A
amp-HASH.js gzip 503 B 504 B N/A
css-HASH.js gzip 323 B 324 B N/A
dynamic-HASH.js gzip 2.5 kB 2.51 kB N/A
edge-ssr-HASH.js gzip 258 B 259 B N/A
head-HASH.js gzip 353 B 351 B N/A
hooks-HASH.js gzip 370 B 370 B
image-HASH.js gzip 4.21 kB 4.2 kB N/A
index-HASH.js gzip 259 B 259 B
link-HASH.js gzip 2.68 kB 2.67 kB N/A
routerDirect..HASH.js gzip 313 B 314 B N/A
script-HASH.js gzip 386 B 385 B N/A
withRouter-HASH.js gzip 309 B 311 B N/A
1afbb74e6ecf..834.css gzip 106 B 106 B
Overall change 931 B 931 B
Client Build Manifests
vercel/next.js canary vercel/next.js 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default Change
_buildManifest.js gzip 485 B 484 B N/A
Overall change 0 B 0 B
Rendered Page Sizes
vercel/next.js canary vercel/next.js 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default Change
index.html gzip 528 B 528 B
link.html gzip 539 B 540 B N/A
withRouter.html gzip 523 B 522 B N/A
Overall change 528 B 528 B
Edge SSR bundle Size
vercel/next.js canary vercel/next.js 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default Change
edge-ssr.js gzip 2.3 kB 2.3 kB N/A
page.js gzip 2.99 kB 2.99 kB N/A
Overall change 0 B 0 B
Middleware size
vercel/next.js canary vercel/next.js 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default Change
middleware-b..fest.js gzip 626 B 627 B N/A
middleware-r..fest.js gzip 151 B 151 B
middleware.js gzip 466 B 465 B N/A
edge-runtime..pack.js gzip 839 B 839 B
Overall change 990 B 990 B
Next Runtimes
vercel/next.js canary vercel/next.js 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default Change
app-page-exp...dev.js gzip 167 kB 167 kB
app-page-exp..prod.js gzip 96.2 kB 96.2 kB
app-page-tur..prod.js gzip 97.9 kB 97.9 kB
app-page-tur..prod.js gzip 92.4 kB 92.4 kB
app-page.run...dev.js gzip 136 kB 136 kB
app-page.run..prod.js gzip 90.9 kB 90.9 kB
app-route-ex...dev.js gzip 22.1 kB 22.1 kB
app-route-ex..prod.js gzip 14.9 kB 14.9 kB
app-route-tu..prod.js gzip 14.9 kB 14.9 kB
app-route-tu..prod.js gzip 14.7 kB 14.7 kB
app-route.ru...dev.js gzip 21.8 kB 21.8 kB
app-route.ru..prod.js gzip 14.7 kB 14.7 kB
pages-api-tu..prod.js gzip 9.49 kB 9.49 kB
pages-api.ru...dev.js gzip 9.76 kB 9.76 kB
pages-api.ru..prod.js gzip 9.48 kB 9.48 kB
pages-turbo...prod.js gzip 22.3 kB 22.3 kB
pages.runtim...dev.js gzip 23 kB 23 kB
pages.runtim..prod.js gzip 22.3 kB 22.3 kB
server.runti..prod.js gzip 50.4 kB 50.4 kB
Overall change 930 kB 930 kB
build cache Overall increase ⚠️
vercel/next.js canary vercel/next.js 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default Change
0.pack gzip 1.49 MB 1.49 MB ⚠️ +517 B
index.pack gzip 104 kB 104 kB ⚠️ +331 B
Overall change 1.59 MB 1.6 MB ⚠️ +848 B
Commit: a4c5f8b

@ijjk
Copy link
Member

ijjk commented Feb 22, 2024

Tests Passed

@ForsakenHarmony ForsakenHarmony merged commit 93eb32d into canary Feb 22, 2024
70 checks passed
@ForsakenHarmony ForsakenHarmony deleted the 02-21-Remove_default_fallback_behavior_when_route_group_is_missing_a_default branch February 22, 2024 15:13
@github-actions github-actions bot added the locked label Mar 8, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 8, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants