True when message looks like a transient transport/download failure of the
engine binary (worth one retry) rather than a genuine corrupt-module or
validation error (which must propagate immediately so real bugs aren't
masked).
Per the WebAssembly Web API, the streaming loader validates the HTTP response
(status, MIME, CORS) and rejects with a TypeError BEFORE compiling, so only
those transport failures are retry-worthy. Invalid bytes (corrupt module,
wrong magic header) reject with a CompileError — retrying just refetches
the same bad bytes, so those fail fast.
True when
messagelooks like a transient transport/download failure of the engine binary (worth one retry) rather than a genuine corrupt-module or validation error (which must propagate immediately so real bugs aren't masked).Per the WebAssembly Web API, the streaming loader validates the HTTP response (status, MIME, CORS) and rejects with a
TypeErrorBEFORE compiling, so only those transport failures are retry-worthy. Invalid bytes (corrupt module, wrong magic header) reject with aCompileError— retrying just refetches the same bad bytes, so those fail fast.