True when an error looks like a content-hashed WASM binary that 404'd / was
served with the wrong MIME type because the deployment rotated under a
still-open tab. Matches the browser-specific phrasings:
Firefox: Response has unsupported MIME type 'text/plain…' expected 'application/wasm'
status-first variants: a WebAssembly compile that failed because the
response was a non-OK HTTP status (the asset is simply gone).
the dynamic-import sibling: Failed to fetch dynamically imported module … .wasm.
The message may be wrapped (e.g. Geometry worker error: <original>), so the
match is a substring test rather than an exact compare. Genuine
module-validation failures (CompileError, bad magic word) are intentionally
NOT matched — those are real corruption, not version skew, and a reload would
loop without fixing them.
True when an error looks like a content-hashed WASM binary that 404'd / was served with the wrong MIME type because the deployment rotated under a still-open tab. Matches the browser-specific phrasings:
Response has unsupported MIME type 'text/plain…' expected 'application/wasm'Incorrect response MIME type. Expected 'application/wasm'.WebAssemblycompile that failed because the response was a non-OK HTTP status (the asset is simply gone).Failed to fetch dynamically imported module … .wasm.The message may be wrapped (e.g.
Geometry worker error: <original>), so the match is a substring test rather than an exact compare. Genuine module-validation failures (CompileError, bad magic word) are intentionally NOT matched — those are real corruption, not version skew, and a reload would loop without fixing them.