npm i neon-hello could not be complete in Arch(WSL2) and Windows ( maybe, the other platforms )

[usagi]

I tried to use the neon-hello npm package because the NEON official instruction of Basic/Electron Apps required this. But, the package is broken maybe.

1. npm i neon-hello in Arch Linux ( on WSL2 )

> neon-hello@0.1.1 install /mnt/c/Users/usagi/tmp/z/wsl/electron-quick-start/node_modules/neon-hello
> neon build

neon info forcing rebuild for new build settings
neon info running cargo
    Updating crates.io index
  Downloaded neon-build v0.1.23
  Downloaded neon v0.1.23
  Downloaded neon-runtime v0.1.23
  Downloaded cslice v0.2.0
  Downloaded ucd-util v0.1.8
   Compiling memchr v2.3.3
   Compiling regex v0.2.11
   Compiling lazy_static v1.4.0
   Compiling ucd-util v0.1.8
   Compiling utf8-ranges v1.0.4
   Compiling gcc v0.3.55
   Compiling neon-build v0.1.23
   Compiling cslice v0.2.0
   Compiling semver-parser v0.7.0
   Compiling thread_local v0.3.6
   Compiling regex-syntax v0.5.6
   Compiling semver v0.9.0
   Compiling neon v0.1.23
   Compiling neon-hello v0.1.0 (/mnt/c/Users/usagi/tmp/z/wsl/electron-quick-start/node_modules/neon-hello/native)
   Compiling aho-corasick v0.6.10
   Compiling neon-runtime v0.1.23
error: failed to run custom build command for `neon-runtime v0.1.23`

Caused by:
  process didn't exit successfully: `/mnt/c/Users/usagi/tmp/z/wsl/electron-quick-start/node_modules/neon-hello/native/target/release/build/neon-runtime-dfcca0777b9857d7/build-script-build` (exit code: 101)
--- stdout
Skipping node-gyp installation as part of npm install.
added 96 packages from 70 contributors and audited 184 packages in 2.296s
found 7 vulnerabilities (3 low, 1 moderate, 3 high)
  run `npm audit fix` to fix them, or `npm audit` for details

> @ build-release /home/usagi/.cargo/registry/src/github.com-1ecc6299db9ec823/neon-runtime-0.1.23
> node-gyp build

make: Entering directory '/home/usagi/.cargo/registry/src/github.com-1ecc6299db9ec823/neon-runtime-0.1.23/build'
  CXX(target) Release/obj.target/neon/src/neon.o
make: Leaving directory '/home/usagi/.cargo/registry/src/github.com-1ecc6299db9ec823/neon-runtime-0.1.23/build'
TARGET = Some("x86_64-unknown-linux-gnu")
TARGET = Some("x86_64-unknown-linux-gnu")
HOST = Some("x86_64-unknown-linux-gnu")
AR_x86_64-unknown-linux-gnu = None
AR_x86_64_unknown_linux_gnu = None
HOST_AR = None
AR = None
TARGET = Some("x86_64-unknown-linux-gnu")
TARGET = Some("x86_64-unknown-linux-gnu")
running: "ar" "crs" "/mnt/c/Users/usagi/tmp/z/wsl/electron-quick-start/node_modules/neon-hello/native/target/release/build/neon-runtime-9af98bb1138b136b/out/libneon.a" "build/Release/obj.target/neon/src/neon.o"
cargo:warning=ar: build/Release/obj.target/neon/src/neon.o: No such file or directory
exit code: 1

--- stderr
In file included from ../node_modules/nan/nan_converters.h:67,
                 from ../node_modules/nan/nan.h:202,
                 from ../src/neon.cc:2:
../node_modules/nan/nan_converters_43_inl.h: In static member function 'static Nan::imp::ToFactoryBase<v8::Boolean>::return_t Nan::imp::ToFactory<v8::Boolean>::convert(v8::Local<v8::Value>)':
../node_modules/nan/nan_converters_43_inl.h:18:49: error: cannot convert 'v8::Local<v8::Context>' to 'v8::Isolate*'
   18 |       val->To ## TYPE(isolate->GetCurrentContext())                            \
      |                       ~~~~~~~~~~~~~~~~~~~~~~~~~~^~
      |                                                 |
      |                                                 v8::Local<v8::Context>
(abbr.)

2. npm i neon-hello in Windows:

> neon-hello@0.1.1 install C:\Users\usagi\tmp\z\electron-quick-start\node_modules\neon-hello
> neon build

neon info forcing rebuild for new build settings
neon info running cargo
    Updating crates.io index
   Compiling memchr v2.3.3
   Compiling regex v0.2.11
   Compiling ucd-util v0.1.8
   Compiling lazy_static v1.4.0
   Compiling utf8-ranges v1.0.4
   Compiling gcc v0.3.55
   Compiling neon-build v0.1.23
   Compiling cslice v0.2.0
   Compiling semver-parser v0.7.0
   Compiling thread_local v0.3.6
   Compiling regex-syntax v0.5.6
   Compiling semver v0.9.0
   Compiling neon v0.1.23
   Compiling neon-hello v0.1.0 (C:\Users\usagi\tmp\z\electron-quick-start\node_modules\neon-hello\native)
   Compiling aho-corasick v0.6.10
   Compiling neon-runtime v0.1.23
error: failed to run custom build command for `neon-runtime v0.1.23`

Caused by:
  process didn't exit successfully: `C:\Users\usagi\tmp\z\electron-quick-start\node_modules\neon-hello\native\target\release\build\neon-runtime-e30d3e1381e0a7a5\build-script-build` (exit code: 101)
--- stdout
'Skipping node-gyp installation as part of npm install.'
audited 184 packages in 1.415s
found 7 vulnerabilities (3 low, 1 moderate, 3 high)
  run `npm audit fix` to fix them, or `npm audit` for details
cargo:node_arch=x64
cargo:node_root_dir=C:\\Users\\usagi\\AppData\\Local\\node-gyp\\Cache\\13.5.0
cargo:node_lib_file=C:\\\\Users\\\\usagi\\\\AppData\\\\Local\\\\node-gyp\\\\Cache\\\\13.5.0\\\\<(target_arch)\\\\node.lib

> @ build-release C:\Users\usagi\.cargo\registry\src\github.com-1ecc6299db9ec823\neon-runtime-0.1.23
> node-gyp build


C:\Users\usagi\.cargo\registry\src\github.com-1ecc6299db9ec823\neon-runtime-0.1.23>if not defined npm_config_node_gyp (node "C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" build )  else (node "C:\Program Files\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" build )
Building the projects in this solution one at a time. To enable parallel build, please add the "-m" switch.
  neon.cc
C:\Users\usagi\.cargo\registry\src\github.com-1ecc6299db9ec823\neon-runtime-0.1.23\node_modules\nan\nan_converters_43_inl.h(22,1): error C2664: 'v8::Local<v8::Boolean> v8::Value::ToBoolean(v8::Isolate *) const': cannot convert argument 1 from 'v8::Local<v8::Context>' to 'v8::Isolate *' [C:\Users\usagi\.cargo\registry\src\github.com-1ecc6299db9ec823\neon-runtime-0.1.23\build\neon.vcxproj]
(abbr.)

---

The enviroments:

1. Arch Linux

• Arch Linux / 4.19.84-microsoft-standard updating the project to make use of a newer version of neon bindings #1 SMP Wed Nov 13 11:44:37 UTC 2019 x86_64 GNU/Linux
• Node.js 13.11.0
• Rust toolchain stable-x86_64-unknown-linux-gnu / 1.42.0 (b8cedc004 2020-03-09)
• gcc 9.3.0 / llvm 0.0.1
• neon 0.4.0

2. Windows

• Windows 10 ( 64-Bit ) 10.0.19041.153
• Node.js 13.5.0 / npm 6.13.4
• Rust toolchain stable-x86_64-pc-windows-msvc / rustc 1.42.0 (b8cedc004 2020-03-09)
• MSVS 2019 16.4.2 / cl 19.24.28314 for x64
• neon 0.4.0

[usagi]

FYI:

1. See also: https://github.com/dherman/neon-hello/network
2. In now, the fork https://github.com/amilajack/neon-hello is maintained; npm i @amilajack/neon-hello, it works in now.