Is any one maintaining this?

Question

Is any one maintaining this?

surfjedi opened this issue 7 years ago · comments

Jameson Little · Answer 1 · Tue Nov 14 2017 00:19:17 GMT+0800 (China Standard Time)

I don't have an active interest in it. I forked it from something that was kind of slow (ported from Java IIRC), so I cleaned it up and fixed some of the big CPU sucks, but it's really not that useful. The browser already does gzip decompression, which fits 90% of use cases, and I mostly built this in conjunction with tar-js (and tar-async) because I had some projects where I was collecting a bunch of data and sending them all to a backend and tar+gzip was convenient.

Those projects are now obsolete and I now consider JS-based tar and gzip to be a really bad idea. If you want it for node.js, use the built-in Zlib stuff. If you want it for the browser, rethink why you want it and there's probably a better solution.

If you want to maintain it, I'll give you commit access.

Sergey Ponomarev · Answer 2 · Fri Nov 02 2018 05:03:53 GMT+0800 (China Standard Time)

Hi @beatgammit can you mention in README the status of project.
I found some alternative https://github.com/Stuk/jszip but for zip files while I need gzip:(

Mykola Golubyev · Answer 3 · Mon Jan 21 2019 11:44:05 GMT+0800 (China Standard Time)

Hi, I am very happy that I found this project. My use case is to build self contained html reports. Reports are dynamic in nature and use ReactJS to display data. Data is embedded as json inside html page. And html page is being generated at build time.

Data can get quite large and so I need to start compressing it (testingisdocumenting/webtau#257)

I deliberately want reports to be self contained (be able to email or slack one) and therefore I cannot rely on backend gzip.

Thank you for making this library. I read that there are edge cases that this may not support, but so far it worked in a limited testing.