ALT Before and after the same Nuxt development error. Nuxt 4.5.2 gives the generic heading ‘An error has occurred’; the current my-bad renderer in Nuxt 4.6 puts ‘Cannot read properties of undefined (reading name)’ first, followed by the failing expression. Notes explain the clearer starting point and expanding callers or component ancestry when needed.

ALT Two views of the same failing frame. Original TypeScript points to shared/directory.ts:8:20; compiled JavaScript points to 4:18. Annotations explain how the highlight and caret locate the expression, source maps connect generated code to TypeScript, file actions open the editor, and copy location shares the precise position. Editor links retain the original source target.

ALT Application callers, optional framework frames and component ancestry in the current Nuxt development error renderer. Notes explain tracing the call that supplied the arguments, hiding library internals while following application code, preserving frame order, revealing framework detail for library debugging, and opening a captured component source file. Execution and UI hierarchy answer different questions.

ALT The Copy error split button and its menu. The primary action copies the diagnosis and source for an issue. Named menu choices offer Markdown, a prompt giving an agent the task and error context, or structured JSON for scripts and tools. All formats use the same report. Purple annotations explain each format’s purpose without covering the controls.