Couldn't be built successfully about node-gyp

[cclauss]

https://github.com/nodejs/node-gyp/tree/main/docs#node-pre-gyp-is-no-longer-maintained

[zN3utr4l]

Node-gyp versions were locked by dependency with @serialport/bindings-cpp@npm:12.0.1, manually updating to the latest version the error changes and becomes:

prebuild-install warn install No prebuilt binaries found (target=6 runtime=napi arch=arm libc= platform=linux)
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | win32 | x64
gyp info find Python using Python version 3.12.3 found at "C:\Python312\python.exe"

gyp http GET https://nodejs.org/download/release/v18.20.2/node-v18.20.2-headers.tar.gz
gyp http 200 https://nodejs.org/download/release/v18.20.2/node-v18.20.2-headers.tar.gz
gyp http GET https://nodejs.org/download/release/v18.20.2/SHASUMS256.txt
gyp http 200 https://nodejs.org/download/release/v18.20.2/SHASUMS256.txt
gyp WARN install got an error, rolling back install
gyp ERR! configure error 
gyp ERR! stack TypeError: Cannot destructure property 'libUrl' of 'release[arch]' as it is undefined.
gyp ERR! stack at downloadNodeLib (G:\TestProj\\test\server\node_modules\node-gyp\lib\install.js:322:15)
gyp ERR! stack at go (G:\TestProj\\test\server\node_modules\node-gyp\lib\install.js:263:20)
gyp ERR! stack at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
gyp ERR! stack at async install (G:\TestProj\\test\server\node_modules\node-gyp\lib\install.js:63:18)
gyp ERR! stack at async getNodeDir (G:\TestProj\\test\server\node_modules\node-gyp\lib\configure.js:79:7)
gyp ERR! stack at async run (G:\TestProj\\test\server\node_modules\node-gyp\bin\node-gyp.js:81:18)
gyp ERR! System Windows_NT 10.0.22631
gyp ERR! command "D:\\Program Files\\nodejs\\node.exe" "G:\\Roboqbo\\qbo-5\\server\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd G:\TestProj\\test\server\node_modules\sqlite3
gyp ERR! node -v v18.20.2
gyp ERR! node-gyp -v v10.1.0
gyp ERR! not ok 

[mokagio]

Looks like the update might have solve the EINVAL error, but just in case, I had success with the { shell: true } approach suggested in https://nodejs.org/en/blog/vulnerability/april-2024-security-releases-2#command-injection-via-args-parameter-of-child_processspawn-without-shell-option-enabled-on-windows-c

However, I was in control of the spawn call, whereas when interacting with this library, one is not because the call is in the library.