When zipping a directory, the zip file is always created in its parent directory regardless of the desired path

Sample package.json:

{
  "name": "zip-test",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "cross-zip ./parent/child/grandchild output.zip"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "cross-zip-cli": "^1.0.0"
  }
}

Make a nested directory structure:

mkdir -p parent/child/grandchild
echo "foo" > parent/child/grandchild/data.txt

Run the script:

$ npm run test

> zip-test@1.0.0 test /Users/sepiaj/ws/zip-test
> cross-zip ./parent/child/grandchild ./output.zip

Expected result: The zip file appears in the CWD (or in this case, the root of the project), as a sibling to package.json.

Actual result: The zip file shows up in parent/child/.

Reproduce the issue using the package.json script and the nested parent/child/grandchild directory structure shown in the report. Start at the cross-zip CLI entry point and trace how the input directory and output.zip paths are resolved; done means the archive is created in the current working directory as expected.