The documentation only states that the system supports node-js streams.

In my example I went ahead and tried to create a file using csv-stringify, which creates a writeable stream and push it to zip.file() function, which didn't work.

Do you see the possibility to introduce a writeable stream to this library?

At least the docs should receive an update here specially mentioning readabl

Or at least, make it use this by default. The reason being that ByExtension() supports many more formats.

I am following the get started guide found here and I was able to create a zip file from within firebase cloud functions and then successfully uploaded it to google storage.

Once I download it to my mac, the zip file gets extracted and becomes a CPGZ file and expanding that creates a ZIP and so on...

Any ideas what's going on?

It’d be super nice if libarchive aka libCVE had proper, human-readable changelogs with references to security fixes. Right now the NEWS file is so incomplete as to be useless, and the release notes page on the wiki hasn’t been updated in ages.

Document with markdown:
(samples could also be unit tests for some copy/pasting to make it easier to maintain when breaking changes occur)

• Basic Archive usage

• Basic Reader usage

• Basic Writer usage

• Options usage around leaving streams open

• Archive Encoding usage with auto-detect

Talking about https://docs.pyfilesystem.org/en/latest/reference/walk.html#fs.walk.BoundWalker.dirs and maybe walk.files is affected as well.

The documentation talks about (emphasis by me):

dirs(path='/', **kwargs)
Walk a filesystem, yielding ABSOLUTE paths to directories.

and

filter_dirs (list, optional) – A list of patterns that will be used to match directori

The documentation of the filter option is misleading:

Filter out files before extracting

That's not really true. When you use decompress (say, with decompress-tar or decompress-unzip), it fully decompresses the entire tarball into memory before applying the filter. If you're not using the output feature, the filter option is entirely equivalent to just using Array.filter yourself o

Your default levels for ZSTD seem a little wonky:

• TURBO: ZSTD is missing, it should be -5 | --fast=5 (the fastest level currently available). This should push it into LZ4 territory.
• EFFICIENT should probably include 3, ZSTD's default level.
• OPTIMAL (meaning best trade off?) should probably be 20, as 22 balloons memory usa