Handle zipfile entry error and forward to onEntryError callback option

[kiejo]

This prevents the node process from crashing in case of a zipfile error.
I also created a test case to ensure it works as expected. The zip file used in the test has an entry with an absolute path, which causes the yauzl library to emit an error, which causes the node process to crash if not handled.

[danrzeppa]

Why not just call cb passing the error? What's the advantage of having an optional onEntryError callback? Does anyone really want the current behavior of crashing the node process?

[kiejo]

I'm sorry for the late response.

Why not just call cb passing the error? What's the advantage of having an optional onEntryError callback?

A zip file can contain many files of which only one or a few files cause a zipfile error. In such a case the overall zip extraction succeeds with only a few files missing from the output. I think that calling the onEntryError for every zipfile error during the extraction is a better solution than signaling a complete failure by calling the cb after the first zipfile error. It allows the user of the library to work with the successfully extracted files and to optionally handle any failed files.

Does anyone really want the current behavior of crashing the node process?

I don't think anyone wants this behavior, which is why I set up an error listener regardless of whether an onEntryError callback is supplied. This prevents the node process from crashing for all users.

[malept]

Closing in favor of #67