max-mapper / max-mapper/extract-zip
Invalid non-string/buffer chunk
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 398
- Forks
- 144
- PR merge metrics
- No merged PRs in 30d
Description
Hi, I'm getting Invalid non-string/buffer chunk error on any .zip file I've tested.
I'm passing a path to the file, like so
var extract = require('extract-zip')
extract('c:\\Builds\\test.zip', {dir:'C:\\Builds'}, (err) => {
console.log(err);
})
Any ideas what can go wrong?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the extract call shown in the issue and reproduce the failure with the provided Windows path and ZIP example. Trace how that input is handled to identify why the archive is rejected, then verify that the example extracts successfully without the invalid chunk error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100