tar filesystem errors when running npm install

A similar issue has been reported in #841, but in my case I can reproduce it with a test repo. Try this:

```
> apk add node npm
> git clone https://github.com/oliversturm/ish-npm-install-issue.git
> cd ish-npm-install-issue
> npm install
```

A number of deprecation warnings come up first (that's normal for the project), but then you will see endless numbers of `ENOENT` errors from `tar`.

Btw, it crossed my mind that it might be the fault of the busybox tar command - but it's not, the problem remains the same if I do `apk add tar` to get GNU tar and then try again.

Start by cloning the test repository and running the apk, git clone, and npm install commands described in the issue. Investigate the repeated tar ENOENT errors, including the result after installing GNU tar; done means the reproduction no longer produces endless filesystem errors during npm install.

Written by the indexing model from the issue text.