Yauzl-mac NPM | npm.io

Unzipping with `yauzl` with added support for Mac OS Archive Utility ZIP files

What it does

Drop-in replacement for yauzl unzipper module, adding support for ZIP files created with Mac OS Archive Utility.

Mac OS Archive Utility creates ZIP files which are corrupt according to the ZIP file spec where either:

Archive is larger than 4GB
Any file in the archive larger than 4GB
Archive contains more than 65535 files

yauzl, and many other unzip applications, cannot unzip such files.

This module is based on yauzl and parses the malformed metadata that Mac OS Archive Utility creates to be able to unzip these files successfully.

There are no tests due to the difficulties of deploying ZIP files to CI which are large enough to reproduce the faulty behavior in Mac OS Archive Utility, but has been tested this on thousands of ZIP files, including hundreds of malformed Mac OS Archive Utility files, and it successfully unzips all the examples.

Usage

API is identical to yauzl, except set the option supportMacArchiveUtility: true when calling .open(), .fromFd(), .fromBuffer() or .fromRandomAccessReader().

const yauzl = require('yauzl-mac');

yauzl.open(
  '/path/to/file.zip',
  { supportMacArchiveUtility: true },
  function(err, zipfile) {
    /* ... usual API ... */
  }
);

Promises

You can combine with yauzl-promise for a promise-based API.

const yauzlMac = require('yauzl-mac');
const yauzl = require('yauzl-promise').useYauzl(yauzlMac);

// Now use yauzl with promisified API

Other useful additions to `yauzl`

yauzl-crc - yauzl with CRC32 checksum verification

Versioning

This module follows semver. Breaking changes will only be made in major version updates.

All active NodeJS release lines are supported (v16+ at time of writing). After a release line of NodeJS reaches end of life according to Node's LTS schedule, support for that version of Node may be dropped at any time, and this will not be considered a breaking change. Dropping support for a Node version will be made in a minor version update (e.g. 1.2.0 to 1.3.0). If you are using a Node version which is approaching end of life, pin your dependency of this module to patch updates only using tilde (~) e.g. ~1.2.3 to avoid breakages.