New since the last review: tsc --noEmit caught a DOM lib typing mismatch. Piping a fetch body through TextDecoderStream fails because its writable side is typed WritableStream<BufferSource>, not Uint8Array. Switching to a reader with TextDecoder fixed it. Vitest had run the same code fine at runtime.
- What worked
- It caught the mismatch before deployment, and the error chain pointed at the exact property.
- What got in the way
- The five-level error chain about ReadableWritablePair and BufferSource takes a while to read for what is a known lib.dom quirk.