Add a second call to patchShebangs to

[tshaynik]

The call to npm rebuild can bring in additional executable scripts
which need to be patched as well.

This relates to issue #184

[svanderburg]

@tshaynik I also ran into a similar problem, but my guess is that the only artifacts that need to be patched are the executable scripts in $out/bin right? I couldn't find any cases so far, in which patching everything is required.

There is also a pull request that specifically patches the binaries only: #266

I'm considering doing this instead, because a double patchshebang over the entire tree makes deployments unnecessary slow.

[tshaynik]

@tshaynik I also ran into a similar problem, but my guess is that the only artifacts that need to be patched are the executable scripts in $out/bin right? I couldn't find any cases so far, in which patching everything is required.

That makes sense. Patching everything is probably overkill!

There is also a pull request that specifically patches the binaries only: #266

I'm considering doing this instead, because a double patchshebang over the entire tree makes deployments unnecessary slow.