next.js

1287f9a0 - Turbopack: show specific SWC error messages as error titles (#91022)

Turbopack: show specific SWC error messages as error titles (#91022) ### What? Changes Turbopack's error overlay to show specific SWC diagnostic messages as the error title instead of generic messages like "Parsing ecmascript source code failed" or "Ecmascript file had an error". ### Why? Previously, all SWC parse/analysis errors in Turbopack showed a generic title (e.g. "Parsing ecmascript source code failed") in the redbox header, with the actual specific error message buried in the description below the code frame. This made it harder for developers to quickly understand what went wrong. **Before:** ``` Parsing ecmascript source code failed > 1 | export default () => <div/ | ^ Expected '>', got '<eof>' ``` **After:** ``` Expected '>', got '<eof>' > 1 | export default () => <div/ | ^ Parsing ecmascript source code failed ``` ### How? **Core change** in `turbopack/crates/turbopack-swc-utils/src/emitter.rs`: When the `IssueEmitter` has a `self.title` set (the generic title like "Parsing ecmascript source code failed"), the SWC diagnostic message is now used as the issue title, and the generic title is demoted to the description. When `self.title` is not set, the existing behavior is preserved (first line of message becomes title, rest becomes description). **Test updates** across ~15 test files: Updated all `isTurbopack` branches in test expectations to reflect the swapped title/description. Only Turbopack-specific branches were modified; webpack and rspack expectations are unchanged. **New test suite** (`test/development/app-dir/ecmascript-error-title/`): Dedicated tests verifying that both syntax errors (e.g. `Expected '>', got '<eof>'`) and analysis errors (e.g. `the name 'Table' is defined multiple times`) show the specific SWC message as the redbox title. **Turbopack snapshot updates:** 4 snapshot files renamed to reflect new titles (e.g. `Parsing ecmascript source code failed-*.txt` → `Expression expected-*.txt`). --------- Co-authored-by: Claude <noreply@anthropic.com>