Instant Insights: When unable to complete validation provide a filename for the unvalidated boundary (#93770)
The error message previously did not say which parallel route slot
couldn't be validated. Now it poitns to the nearest segment below the
validation boundary. The idea is you go look abive this and figure out
if it is intentional that this segment isn't rendered in the current
context. If so you can ignored the warning (it should ideally not even
be presented as a normal error) but if it is unintentional you
investigate why you aren't SSRing this slot or you mark the slot as
intentionally blocking so it doesn't get validated.
next.js
e2b0d2ea - Instant Insights: When unable to complete validation provide a filename for the unvalidated boundary (#93770)
