-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Completion callback never invoked! #1887
Comments
I have the same problem. |
We have the same problem on Linux: gyp info it worked if it ends with ok |
Me either. MacOS 10.14.5
|
The same issue with Node v12.9.0
|
Same with NodeJS v8.16.1, node-pre-gyp@0.13.0 and node-gyp@4.0.0 Repro on linux, windows and macOS @cclauss |
And this magically started to work again for me. Bogus server ? |
Error: gyp info it worked if it ends with ok |
Its working now. Could really have been a server problem. |
The issue was caused by |
C:\Users\Leon\Desktop\quickstart\addon>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" install ) else (node "C:\Users\Leon\AppData\Roaming\npm\node_modules\node-gyp\bin\node-gyp.js" install ) gyp info it worked if it ends with ok gyp info using node-gyp@5.0.3 gyp info using node@12.10.0 | win32 | x64 gyp http GET https://nodejs.org/download/release/v12.10.0/node-v12.10.0-headers.tar.gz gyp http 200 https://nodejs.org/download/release/v12.10.0/node-v12.10.0-headers.tar.gz gyp ERR! Completion callback never invoked! gyp ERR! System Windows_NT 10.0.18362 gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Leon\\AppData\\Roaming\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "install" gyp ERR! cwd C:\Users\Leon\Desktop\quickstart\addon gyp ERR! node -v v12.10.0 gyp ERR! node-gyp -v v5.0.3 gyp ERR! This is a bug in
node-gyp. gyp ERR! Try to update node-gyp and file an Issue if it does not help: gyp ERR! <https://github.com/nodejs/node-gyp/issues>
The text was updated successfully, but these errors were encountered: