fix: render error boundaries inside their layout chain - #1413

Merged

vivek7405 merged 20 commits into

mainfrom

fix/error-boundary-layouts

Aug 15, 2026

Commits on Aug 14, 2026

fix: render error boundaries inside their layout chain
vivek7405
committed
4ee36d4
test: prove a nav into a throwing page is a soft navigation
vivek7405
committed
5760cc3
test: raise the ssr barrel floor for the two boundary helpers
vivek7405
committed
bf00e9a
test: narrow the error-boot assertion to what actually rendered
vivek7405
committed
870d45e
fix: never advertise a layout region the boundary did not render
vivek7405
committed
170310a
chore: drop verification scratch apps swept in by git add -A
vivek7405
committed
f9b062c
fix: close three gaps opened by shipping the boundary boot set
vivek7405
committed
fc2fce3
fix: do not report a control-flow throw as a crash, and stop losing the 500 one
vivek7405
committed
7b26242
fix: report a boundary-path failure once, and never over the root cause
vivek7405
committed
05991db
fix: dedupe boundary reports by cause, not by "one per request"
vivek7405
committed
f72c16d
fix: key boundary-report dedup on the stage, and make the key total
vivek7405
committed
e2ac6d9
fix: stop a boundary crash leaking its message, and formatting one from throwing
vivek7405
committed
7b24eec
test: assert the 404 fallback body is dev-only
vivek7405
committed
1fe89dc
fix: report a boundary module that throws or fails to load
vivek7405
committed
3afb2d7
fix: report a boundary tree failure once, and wire the unrouted 404 sinks
vivek7405
committed
0af5cf8
fix: record the boundary failure phase instead of inferring it
vivek7405
committed
c0c978c
fix: diagnose a boundary failure by the fallback, not the marker alone
vivek7405
committed
641dca1
fix: do not treat a failed prefetch as a recovery, or re-render a chainless boundary
vivek7405
committed
fdf0e4c
fix: make the tree-failure fixtures runtime-agnostic, and skip a pointless re-render
vivek7405
committed
0ca2e52

Commits on Aug 15, 2026

fix: wrap the DEFAULT boundary page, and use nearest-wins on the form path
vivek7405
committed
f6cf4a5

Navigation Menu

Uh oh!

fix: render error boundaries inside their layout chain - #1413

fix: render error boundaries inside their layout chain#1413
vivek7405 merged 20 commits into
mainfrom
fix/error-boundary-layouts

Commits on Aug 14, 2026

fix: render error boundaries inside their layout chain

test: prove a nav into a throwing page is a soft navigation

test: raise the ssr barrel floor for the two boundary helpers

test: narrow the error-boot assertion to what actually rendered

fix: never advertise a layout region the boundary did not render

chore: drop verification scratch apps swept in by git add -A

fix: close three gaps opened by shipping the boundary boot set

fix: do not report a control-flow throw as a crash, and stop losing the 500 one

fix: report a boundary-path failure once, and never over the root cause

fix: dedupe boundary reports by cause, not by "one per request"

fix: key boundary-report dedup on the stage, and make the key total

fix: stop a boundary crash leaking its message, and formatting one from throwing

test: assert the 404 fallback body is dev-only

fix: report a boundary module that throws or fails to load

fix: report a boundary tree failure once, and wire the unrouted 404 sinks

fix: record the boundary failure phase instead of inferring it

fix: diagnose a boundary failure by the fallback, not the marker alone

fix: do not treat a failed prefetch as a recovery, or re-render a chainless boundary

fix: make the tree-failure fixtures runtime-agnostic, and skip a pointless re-render

Commits on Aug 15, 2026

fix: wrap the DEFAULT boundary page, and use nearest-wins on the form path