worker.js left a rejected start (its async init) unhandled, which a page's Worker error event doesn't see: the page waited for "ready" forever and the render stayed pending until cancelled. The failed start is now re-raised where the page's onerror sees it, like the other worker failures; the job fails with the error and the worker is terminated. Test: apps/effectcraft-web/tests/workers.mjs (worker.js with a stub module whose init rejects; host.js with a worker whose start fails). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018gnTnH3Jmk5zr4tMq1Mc9f |
||
|---|---|---|
| .. | ||
| brand | ||
| fidelity | ||
| images | ||
| agents.md | ||
| architecture.md | ||
| control-protocol.md | ||
| effects.md | ||
| gaps.md | ||
| parity.md | ||
| plugins.md | ||
| preferences.md | ||
| releasing.md | ||
| testing.md | ||
| web.md | ||