Fix build failure

[jjpe]

On MacOS and some Linux distro's the build failure caused by a devDependendy that should have been a dependency seems to be fixed by this commit, as outlined here.

[joelgallant]

This also works for me, I had issues with an in-docker build (joelgallant@7469fd1).

[PSeitz]

@jjpe Can I use this directly from your fork?

[jjpe]

@PSeitz you can but it's completely unsupported, so use at your own risk.

[PSeitz]

@jjpe Sorry I meant to ask how. Not sure how to use it, because the only dependency in my package-lock.json is neon-cli.

[jjpe]

Npm supports both git and path dependencies.
A git dependency to the fork seems easiest to do, as you wouldn't need to clone the fork.

For more info have a look at https://docs.npmjs.com/files/package.json (apologies for the ugly link)

[PSeitz]

Ok now I got it, the dependency has to be specified in the Cargo.toml, because from there it starts the npm install

[patch.crates-io]
neon-runtime = { git = 'https://github.com/jjpe/neon' }

This solved the compile issue!
Would really appreciate if this gets merged.

[dherman]

Thanks @jjpe for this PR, and for your patience 😊