ConstThe error is the same whatever inflates the data, and the error the codec raised is kept as its
cause: the TypeError of a native DecompressionStream, whose message depends on the engine,
or the error of the bundled WASM or pure-JS codec. An error raised while reading the data, e.g.
by the reader of the zip file or by the decryption of the entry, is not a codec failure and
reaches the caller unchanged.
Bytes trailing a complete DEFLATE stream (e.g. a wrong compressedSize) are rejected by every
codec, the native DecompressionStream (on Node.js, with ERR_TRAILING_JUNK_AFTER_STREAM_END
as the code of the cause) and the bundled WASM and pure-JS codecs alike, except that with
ZipReaderOptions#checkCrc32 set the native inflater of Node.js reports them as
ERR_INVALID_CRC32, see that error. Any data that is returned is always validated against
the entry's uncompressed size (and CRC when ZipReaderOptions#checkCrc32 is set), so it is
never silently truncated.
Invalid compressed data error, thrown when the codec rejects the compressed data of an entry.