Zack Tanner aa48b65f9a log a dev warning when a missing parallel slot results in a 404 (#60186) ... ### What & Why? When visiting a route that attempts to render a slot with no page & no default, the fallback behavior is to trigger a 404. However this can lead to a confusing development experience for complex parallel routing cases as you might not realize a default is missing, or which slot is causing the error. Previous issues where this caused confusion: - https://github.com/vercel/next.js/issues/51805 - https://github.com/vercel/next.js/issues/49569 ### How? This is a dev-only modification to track parallel slots that are using the default fallback (aka missing). When the `NotFoundBoundary` is triggered in development mode, this will log a warning about why it 404ed, along with a list of slot(s) that were determined to be missing.  ### Future We should eventually lift this into some sort of dev-only UI to help catch it when not monitoring the browser console (similar to the error overlay). However, this will require some design thought and isn't necessary for the first iteration. Closes NEXT-1798		2024-01-04 07:56:20 -08:00
..
app	log a dev warning when a missing parallel slot results in a 404 (#60186)	2024-01-04 07:56:20 -08:00
parallel-route-not-found.test.ts	log a dev warning when a missing parallel slot results in a 404 (#60186)	2024-01-04 07:56:20 -08:00