Run testbinary after install and fallback to build if it fails

[recrsn]

Sometimes, the pre-built binaries are ABI incompatible with host packages. node-pre-gyp reports a successful install and node subsequently segfaults. (kelektiv/node.bcrypt.js#528)

This case is becoming quite common: People are wanting to install pre-built binaries in systems using musl libc, while we only provide binaries linked against glibc. We want to fall-back to source compile in this case.

[springmeyer]

You can do this by putting this in your package.json:

    "scripts": {
        "install": "node-pre-gyp install testbinary --fallback-to-build"
    },

refs #297

[oohnoitz]

I tried that install script, but it seems that this doesn't really trigger a rebuild at all. What I've noticed is that it does the following:

• adds { name: 'build', args: ['rebuild'] } to the todo stack if it fails to fetch the binaries
• runs the testbinary which fails because it can't locate the binaries to test
• it doesn't attempt to build the binaries since the testbinary command returns an error triggering the process to get killed
• since the process got killed, it doesn't bother to compile the build (also couldn't find any code where testbinary also uses the same --fallback-to-build logic as install

[coreprocess]

@agathver node-pre-gyp just released a new version, which support the {libc} token in the path and package name variables. The token resolves to glibc or musl.

See:

• https://github.com/mapbox/node-pre-gyp/blob/master/CHANGELOG.md#0639
• https://github.com/mapbox/node-pre-gyp/blob/master/README.md#versioning
• Working example: https://github.com/core-process/snapsync/blob/master/node/package.json#L14-L15