request: browser support

max-mapper commented 10 years ago

it would be sweet to use this client-side, but some things would need to change first:

remove assumption that a filename will be passed in and a folder will be created + extracted to
instead have an abstract interface that requests byte ranges (e.g. what getBuffer is doing) but is decoupled from fs. that way it can be hooked up to FileReader in the browser. require('fs') would have to move to separate node-only file from the extraction logic. the extraction logic would be generic so that it can run in the browser or in node
also abstract the extraction so that instead of passing in a destination folder you can just get a readable stream for each file file extraction

sindresorhus commented 10 years ago

remove assumption that a filename will be passed in and a folder will be created + extracted to instead have an abstract interface that requests byte ranges

:+1: This should really be the case regardless of browser support. Requiring an actual file makes it hard to use in cases where you just operate in-memory. Like with gulp.

wibblymat commented 10 years ago

This seems like it would be a very hard thing to do. There are very many places that assume you are using Node. How good is browserify with things like this?

timdp commented 9 years ago

:+1:

Would love this. Any decent alternatives yet?

sindresorhus commented 9 years ago

@timdp https://stuk.github.io/jszip/

timdp commented 9 years ago

Right before I saw your comment, I finished writing some Promise wrappers around zip.js. Thanks though. :smile:

bower / decompress-zip

request: browser support #19