question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't install properly

See original GitHub issue
npm i -g node-inspector
npm WARN deprecated hawk@3.1.3: This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated hoek@2.16.3: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated sntp@1.0.9: This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated cryptiles@2.0.5: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated boom@2.10.1: This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).

> v8-profiler@5.7.0 preinstall C:\Program Files\nodejs\node_modules\node-inspector\node_modules\v8-profiler
> node -e 'process.exit(0)'


> v8-debug@1.0.1 preinstall C:\Program Files\nodejs\node_modules\node-inspector\node_modules\v8-debug
> node -e 'process.exit(0)'

C:\Program Files\nodejs\node-inspector -> C:\Program Files\nodejs\node_modules\node-inspector\bin\inspector.js
C:\Program Files\nodejs\node-debug -> C:\Program Files\nodejs\node_modules\node-inspector\bin\node-debug.js

> v8-debug@1.0.1 install C:\Program Files\nodejs\node_modules\node-inspector\node_modules\v8-debug
> node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(404): https://node-inspector.s3.amazonaws.com/debug/v1.0.1/node-v64-win32-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for v8-debug@1.0.1 and node@10.16.0 (node-v64 ABI, unknown) (falling back to source compile with node-gyp)
node-pre-gyp ERR! Tried to download(undefined): https://node-inspector.s3.amazonaws.com/debug/v1.0.1/node-v64-win32-x64.tar.gz
node-pre-gyp ERR! Pre-built binaries not found for v8-debug@1.0.1 and node@10.16.0 (node-v64 ABI, unknown) (falling back to source compile with node-gyp)
gyp ERR! gypconfigure error
 ERR! gypconfigure error
ERR! stack Error: Command failed: C:\Users\Mattaio\AppData\Local\Programs\Python\Python37-32\python.EXE -c import sys; print "%s.%s.%s" % sys.version_info[:3];
gypgyp  ERR!ERR!  stackstack Error: Command failed: C:\Users\Mattaio\AppData\Local\Programs\Python\Python37-32\python.EXE -c import sys; print "%s.%s.%s" % sys.version_info[:3];
   File "<string>", line 1
gypgyp  ERR! ERR!stack    File "<string>", line 1
stackgyp     import sys; print "%s.%s.%s" % sys.version_info[:3];
 gyp ERR!ERR!  stackstack     import sys; print "%s.%s.%s" % sys.version_info[:3];
                                ^
gypgyp  ERR! ERR!stack stack                                ^
gyp SyntaxError: invalid syntax
 gypERR!  ERR!stack  SyntaxError: invalid syntax
stackgyp
ERR!gyp  stackERR!
 gypstack ERR!     at ChildProcess.exithandler (child_process.js:294:12)
 gypstack     at ChildProcess.exithandler (child_process.js:294:12)
 gypERR!  ERR!stack      at ChildProcess.emit (events.js:198:13)
stackgyp     at ChildProcess.emit (events.js:198:13)
 gypERR!  ERR!stack      at maybeClose (internal/child_process.js:982:16)
stack     at maybeClose (internal/child_process.js:982:16)
gypgyp  ERR!ERR!  stackstack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
gyp gypERR!  ERR!System  Windows_NT 10.0.17763
Systemgyp Windows_NT 10.0.17763
 ERR!gyp  commandERR! "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Mattaio\\AppData\\Roaming\\nvm\\v10.16.0\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "configure" "--fallback-to-build" "--module=C:\\Program Files\\nodejs\\node_modules\\node-inspector\\node_modules\\v8-debug\\build\\debug\\v1.0.1\\node-v64-win32-x64\\debug.node" "--module_name=debug" "--module_path=C:\\Program Files\\nodejs\\node_modules\\node-inspector\\node_modules\\v8-debug\\build\\debug\\v1.0.1\\node-v64-win32-x64"
 gyp command "C:\\Program Files\\nodejs\\node.exe" "C:\\Users\\Mattaio\\AppData\\Roaming\\nvm\\v10.16.0\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "configure" "--fallback-to-build" "--module=C:\\Program Files\\nodejs\\node_modules\\node-inspector\\node_modules\\v8-debug\\build\\debug\\v1.0.1\\node-v64-win32-x64\\debug.node" "--module_name=debug" "--module_path=C:\\Program Files\\nodejs\\node_modules\\node-inspector\\node_modules\\v8-debug\\build\\debug\\v1.0.1\\node-v64-win32-x64"
ERR!gyp  cwd C:\Program Files\nodejs\node_modules\node-inspector\node_modules\v8-debug
ERR!gyp  cwdERR! C:\Program Files\nodejs\node_modules\node-inspector\node_modules\v8-debug
 gypnode -v  v10.16.0
ERR!gyp  node -vERR! v10.16.0
gyp node-gyp -v  v3.8.0
ERR!gyp  node-gyp -vERR! v3.8.0
 gyp not okERR!
 not ok
node-pre-gyp ERR! build error
node-pre-gyp ERR! stack Error: Failed to execute 'C:\Program Files\nodejs\node.exe C:\Users\Mattaio\AppData\Roaming\nvm\v10.16.0\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=C:\Program Files\nodejs\node_modules\node-inspector\node_modules\v8-debug\build\debug\v1.0.1\node-v64-win32-x64\debug.node --module_name=debug --module_path=C:\Program Files\nodejs\node_modules\node-inspector\node_modules\v8-debug\build\debug\v1.0.1\node-v64-win32-x64' (1)
node-pre-gyp ERR! stack     at ChildProcess.<anonymous> (C:\Users\Mattaio\AppData\Roaming\nvm\v10.16.0\node_modules\node-inspector\node_modules\node-pre-gyp\lib\util\compile.js:83:29)
node-pre-gyp ERR! stack     at ChildProcess.emit (events.js:198:13)
node-pre-gyp ERR! stack     at maybeClose (internal/child_process.js:982:16)
node-pre-gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
node-pre-gyp ERR! System Windows_NT 10.0.17763
node-pre-gyp ERR! command "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\node-inspector\\node_modules\\node-pre-gyp\\bin\\node-pre-gyp" "install" "--fallback-to-build"
node-pre-gyp ERR! cwd C:\Program Files\nodejs\node_modules\node-inspector\node_modules\v8-debug
node-pre-gyp ERR! node -v v10.16.0
node-pre-gyp ERR! node-pre-gyp -v v0.6.39
node-pre-gyp ERR! not ok
Failed to execute 'C:\Program Files\nodejs\node.exe C:\Users\Mattaio\AppData\Roaming\nvm\v10.16.0\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js configure --fallback-to-build --module=C:\Program Files\nodejs\node_modules\node-inspector\node_modules\v8-debug\build\debug\v1.0.1\node-v64-win32-x64\debug.node --module_name=debug --module_path=C:\Program Files\nodejs\node_modules\node-inspector\node_modules\v8-debug\build\debug\v1.0.1\node-v64-win32-x64' (1)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! v8-debug@1.0.1 install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the v8-debug@1.0.1 install script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\Mattaio\AppData\Roaming\npm-cache\_logs\2019-07-20T13_17_15_013Z-debug.log

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:21
  • Comments:8

github_iconTop GitHub Comments

8reactions
gaborlukcommented, Aug 13, 2019

From the readme:

Since version 6.3, Node.js provides a built-in DevTools-based debugger which mostly deprecates Node Inspector, see e.g. this blog post to get started. The built-in debugger is developed directly by the V8/Chromium team and provides certain advanced features (e.g. long/async stack traces) that are too difficult to implement in Node Inspector.

For Node.js versions >=6.3 , just use the built-in node --inspect index.js, documentation here.

7reactions
davehowsoncommented, Nov 6, 2019

node --inspect does not show network requests though

Read more comments on GitHub >

github_iconTop Results From Across the Web

Windows Won't Install Properly? 5 Tips to Solve All Common ...
Windows Won't Install Properly? 5 Tips to Solve All Common Issues · 1. Remove Unnecessary External Devices · 2. Optimize Your Current Installation....
Read more >
How to troubleshoot Windows Installer errors - Microsoft Support
Right-click Windows Installer, and then click Properties. If the Startup type box is set to Disabled, change it to Manual. Click OK to...
Read more >
8 Ways to Fix Windows 10 if It Won't Install on Your PC
Windows 10 is not installing on your computer? You can start fixing it by checking for driver errors or corrupted updates.
Read more >
[SOLVED] Windows 10 Could Not Complete the Installation + ...
To install Windows on this computer, restart the installation. ... After you have successfully installed the free backup software, ...
Read more >
Why Won't Windows 10 Install From a USB? Causes and Fixes
If your PC USB port isn't working, you obviously can't install Windows 10 from the USB stick. This is because your computer won't...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found