DEFAULT ERROR SCREEN · PROPOSAL FOR REVIEW

Find the failure.
Keep the context.

A quieter first screen, with the evidence still within reach. A comparison with the current my-bad renderer, followed by two ways to explore the call stack: inspect one frame, or read all application frames together.

Before: current libraryAfter: working prototypeSame report · same viewport width

The proposal is implemented in the playground. These changes have not been ported into the library’s default renderer.

REVIEW DECISION

How much should Call stack reveal at once?

The main direction is shared: lead with the message, show useful code and keep supporting evidence close. The remaining choice is how to explore callers.

FocusOpen the frame you want to inspect.StackRead application excerpts together.

Implementation scope

This proposal changes the default error screen’s presentation and interactions. It reuses the existing reports, source maps, cause relationships and log transport. The working prototypes are in the playground; the library renderer has not yet changed.