101arrowz

`fflate`'s philosophy is to avoid validating or checking input and to not allow shorthands except where it yields no impact on bundle size, so this is not going to be...

Interesting idea. Honestly I never really liked the streaming API myself but I wanted near API compatibility with Pako, which was the only popular compression library when I made `fflate`,...

That's quite strange. An idea (maybe a bad one) for your message passing issue is Base64, which should be moderately fast for binary data (as long as you use a...

I'll preface by saying that this is a very niche use case, so even if it is easy to implement I'll have to weigh the bundle size costs to see...

I had forgotten about this issue but what you've proposed does seem compelling. I'll look into the `bgzip` spec and try to implement it for the next release.

OK after looking at the requirements for this it's actually not too difficult. Support for GZIP extra fields will need to be added on the compression side if you want...

Interesting, I've never had to deal with locales so this could be a challenge, but I'll try to implement this when I get the chance. Since it's a larger change...

I've found that Unicode filenames in general are annoying to deal with. You need to set `{ os: 3 }` (Unix) for it to work with the default `zip` included...

That actually seems like a decent solution. I'm assuming no sane person would use cp866 for creating new ZIP files, so just decode support might work OK with a similar...

Could you provide a sample file (or how to generate one) so I can reproduce this?