Redesign the unrendered-segment instant validation overlay#93879
Redesign the unrendered-segment instant validation overlay#93879aurorascharff wants to merge 10 commits into
Conversation
…rcel/next.js into aurorascharff/redesign-unrendered-segment-overlay
Failing test suitesCommit: dcf251d | About building and testing Next.js
Expand output● instant validation - parallel slot configs › dev - initial load › conditional slot rendering › errors when configured children slot is hidden, no cookies ● instant validation - parallel slot configs › dev - client navigation › conditional slot rendering › errors when configured children slot is hidden, no cookies
Expand output● instant validation › dev - initial load › multi-depth fallback deferral › surfaces deferred fallback when no shallower depth has a real error ● instant validation › dev - initial load › unrendered segment file reporting › reports the shallowest unrendered file, not the configured file ● instant validation › dev - initial load › unrendered segment file reporting › reports the boundary segment layout when multiple slots are dropped ● instant validation › dev - client navigation › multi-depth fallback deferral › surfaces deferred fallback when no shallower depth has a real error ● instant validation › dev - client navigation › unrendered segment file reporting › reports the shallowest unrendered file, not the configured file ● instant validation › dev - client navigation › unrendered segment file reporting › reports the boundary segment layout when multiple slots are dropped ... truncated ...
Expand output● instant validation - parallel slot configs › build › conditional slot rendering › errors when configured children slot is hidden, no cookies
Expand output● instant validation › build › multi-depth fallback deferral › surfaces deferred fallback when no shallower depth has a real error ● instant validation › build › unrendered segment file reporting › reports the shallowest unrendered file, not the configured file ● instant validation › build › unrendered segment file reporting › reports the boundary segment layout when multiple slots are dropped
Expand output● instant validation - parallel slot configs › dev - initial load › conditional slot rendering › errors when configured children slot is hidden, no cookies ● instant validation - parallel slot configs › dev - client navigation › conditional slot rendering › errors when configured children slot is hidden, no cookies
Expand output● instant validation › dev - initial load › multi-depth fallback deferral › surfaces deferred fallback when no shallower depth has a real error ● instant validation › dev - initial load › unrendered segment file reporting › reports the shallowest unrendered file, not the configured file ● instant validation › dev - initial load › unrendered segment file reporting › reports the boundary segment layout when multiple slots are dropped ● instant validation › dev - client navigation › multi-depth fallback deferral › surfaces deferred fallback when no shallower depth has a real error ● instant validation › dev - client navigation › unrendered segment file reporting › reports the shallowest unrendered file, not the configured file ● instant validation › dev - client navigation › unrendered segment file reporting › reports the boundary segment layout when multiple slots are dropped ... truncated ...
Expand output● instant validation - parallel slot configs › build › conditional slot rendering › errors when configured children slot is hidden, no cookies
Expand output● instant validation › build › multi-depth fallback deferral › surfaces deferred fallback when no shallower depth has a real error ● instant validation › build › unrendered segment file reporting › reports the shallowest unrendered file, not the configured file ● instant validation › build › unrendered segment file reporting › reports the boundary segment layout when multiple slots are dropped
... truncated to fit in one GitHub comment ... |
What?
A focused dev-overlay redesign and CLI/build message refresh for the "expected segment was not rendered" instant validation warning (PR #93770).
Why?
The wrapper carries no useful source location to point at — the code-frame chrome and Call Stack the overlay rendered before were misleading. Users mostly need to know which segment didn't render and where to set
instant = falseto silence the warning.Demo
81-instant-wrapper-unrendered-segmentHow
dynamic-rendering.ts: leads withRoute "<path>":prefix like every other validation factory, drops the verbose paragraphs in favour of a one-sentence explanation +Ways to fix this:list, and usesinstantnotunstable_instantin the fix bullet.unrendered-segmentGuidanceKindand a dedicated case inerrors.tsxthat drops the code-frame and Call Stack.UnrenderedSegmentInfocomponent renders the route + each unrendered file with the same chrome asCodeFrame, plus open-in-editor.Render the missing segment(render, gray) andAllow no validation(silence, red).