test: stabilize lazy dynamic import error overlay (#98730)
### What? Stabilizes the Turbopack development test that verifies an invalid dynamic-import target stays unparsed until activation, while checking both server compilation output and the browser-visible error overlay afterward. ### Why? Activating the target can trigger an incidental hard reload as Fast Refresh recovers from the error. A one-shot overlay source read can race that document replacement. The test should check the error it owns without requiring a reload or accepting an absent overlay. ### How? The test retains canary's CLI-output assertion and independently retries a live browser-redbox source assertion filtered to the expected parse-error marker. Playwright re-resolves the locator across document changes; both signals must actually contain the marker. ### Verification - Focused Turbopack dev case under six competing CPU workers: 20/20 passed on rebased canary - Complete `lazy-dynamic-imports` Turbopack dev file: 3/3 passed on rebased canary - Related `next/dynamic` error-overlay case: 10/10 passed on rebased canary - Prettier, ESLint, clean merge-tree, and diff checks <!-- NEXT_JS_LLM --> <!-- fleet 2dd4f041-bfb3-4572-9b57-5cb45a2410cd --> --------- Co-authored-by:vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by:
Tobias Koppers <1365881+sokra@users.noreply.github.com>
Showing
Please
register
or
sign in
to comment