Thanks for your answer, Elijah. I know that already, but I would rather
prefer to -not- split my native library into a new package. It is just a
single .cpp binding.gyp file and I don't like the idea of having 2
separate repositories. Thats why I was looking for any sort of option which
would
I think you're looking for something like this:
install: node-gyp rebuild || exit 0
Putting that in the scripts section of your module's package.json will
prevent the installation of the module from failing just because node-gyp
fails.
~Ryan
https://twitter.com/rmgraham
On Jul 11, 2014 8:49 PM,
Hello everyone
I am currently trying to offer an *optional native library* for my own
Node.js package. My library actually works 6+ (up to 20, didn't test
further) times faster than with the plain JS implementation. The drawback:
It requires libcrypto++-dev, otherwise the build will fail.
https://www.npmjs.org/doc/package.json.html#optionalDependencies
On Fri, Jul 11, 2014 at 11:55 AM, Pascal Mathis pmat...@snapserv.net
wrote:
Hello everyone
I am currently trying to offer an *optional native library* for my own
Node.js package. My library actually works 6+ (up to 20, didn't
