Calling `inflate` on data created from `Pako.deflate` returns `(null, null)`See original GitHub issue
Some observations that I noted:
inflate fails with
inflateSync fails with EOF:
This is probably the most important problem since one would expect either data or an error.
decompress works fine:
deflateSync : incorrect header check
It appears as though Pako has a different idea of what constitutes
gzipSync: seems to correspond to
I noted that the builtin
CompressionStream seems to correlate with what Pako does i.e.
'inflate' algorithm for Pako and CompressionStream seem to be the same.
zlib: same as
zip: fails, same as deflate
I’ve no idea what’s going on here (and the issues observed may be with Pako), but I hope the above is useful feedback.
- Created 2 years ago
- Comments:5 (4 by maintainers)