Variable ERR_INVALID_CRC32Const

Remarks

When the inflater verifies the checksum itself, through a gzip trailer that zip.js builds from the stored CRC-32 and uncompressed size, it rejects the trailer as a whole and its error is kept as the cause. A stored uncompressed size larger than the data therefore raises this error too on that route, whereas a stored size smaller than the data raises ERR_INVALID_UNCOMPRESSED_SIZE on every route. Bytes trailing the DEFLATE stream, e.g. a wrong compressedSize, displace that trailer, and an inflater that reports them only once the real trailer has been written, as the one of Node.js does, raises this error in place of ERR_INVALID_COMPRESSED_DATA.