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.

Not able to install node-inspector in OSX 10.12.3

See original GitHub issue

not able to install node-inspector in mac. Getting the following error-

npm WARN lifecycle v8-debug@0.7.7~preinstall: cannot run in wd %s %s (wd=%s) v8-debug@0.7.7 node -e ‘process.exit(0)’ /usr/local/lib/node_modules/.staging/v8-debug-5be573b2 npm WARN lifecycle v8-profiler@5.6.5~preinstall: cannot run in wd %s %s (wd=%s) v8-profiler@5.6.5 node -e ‘process.exit(0)’ /usr/local/lib/node_modules/.staging/v8-profiler-4971d27a /usr/local/bin/node-inspector -> /usr/local/lib/node_modules/node-inspector/bin/inspector.js /usr/local/bin/node-debug -> /usr/local/lib/node_modules/node-inspector/bin/node-debug.js

v8-debug@0.7.7 install /usr/local/lib/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/v0.7.7/node-v51-darwin-x64.tar.gz node-pre-gyp ERR! Pre-built binaries not found for v8-debug@0.7.7 and node@7.6.0 (node-v51 ABI) (falling back to source compile with node-gyp) CXX(target) Release/obj.target/debug/src/debug.o …/src/debug.cc:38:27: error: too few arguments to function call, expected at least 2, have 1 v8::Debug::Call(fn); ~~~~~~~~~~~~~~~ ^ /Users/jagveersingh/.node-gyp/7.6.0/include/node/v8-debug.h:198:3: note: ‘Call’ declared here static MaybeLocal<Value> Call(Local<Context> context, ^ …/src/debug.cc:46:61: error: too few arguments to function call, single argument ‘isolate’ was not specified Isolate* debug_isolate = v8::Debug::GetDebugContext()->GetIsolate(); ~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ /Users/jagveersingh/.node-gyp/7.6.0/include/node/v8-debug.h:248:3: note: ‘GetDebugContext’ declared here static Local<Context> GetDebugContext(Isolate* isolate); ^ …/src/debug.cc:61:67: error: too few arguments to function call, single argument ‘isolate’ was not specified Local<Context> debug_context = v8::Debug::GetDebugContext(); ~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ /Users/jagveersingh/.node-gyp/7.6.0/include/node/v8-debug.h:248:3: note: ‘GetDebugContext’ declared here static Local<Context> GetDebugContext(Isolate* isolate); ^ …/src/debug.cc:66:54: error: too few arguments to function call, single argument ‘isolate’ was not specified debug_context = v8::Debug::GetDebugContext(); ~~~~~~~~~~~~~~~~~~~~~~~~~~ ^ /Users/jagveersingh/.node-gyp/7.6.0/include/node/v8-debug.h:248:3: note: ‘GetDebugContext’ declared here static Local<Context> GetDebugContext(Isolate* isolate); ^ 4 errors generated. make: *** [Release/obj.target/debug/src/debug.o] Error 1 gyp ERR! build error gyp ERR! stack Error: make failed with exit code: 2 gyp ERR! stack at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:276:23) gyp ERR! stack at emitTwo (events.js:106:13) gyp ERR! stack at ChildProcess.emit (events.js:192:7) gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:12) gyp ERR! System Darwin 16.4.0 gyp ERR! command “/usr/local/bin/node” “/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js” “build” “–fallback-to-build” “–module=/usr/local/lib/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64/debug.node” “–module_name=debug” “–module_path=/usr/local/lib/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64” gyp ERR! cwd /usr/local/lib/node_modules/node-inspector/node_modules/v8-debug gyp ERR! node -v v7.6.0 gyp ERR! node-gyp -v v3.5.0 gyp ERR! not ok node-pre-gyp ERR! build error node-pre-gyp ERR! stack Error: Failed to execute ‘/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/usr/local/lib/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64/debug.node --module_name=debug --module_path=/usr/local/lib/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64’ (1) node-pre-gyp ERR! stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/node-inspector/node_modules/node-pre-gyp/lib/util/compile.js:83:29) node-pre-gyp ERR! stack at emitTwo (events.js:106:13) node-pre-gyp ERR! stack at ChildProcess.emit (events.js:192:7) node-pre-gyp ERR! stack at maybeClose (internal/child_process.js:890:16) node-pre-gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) node-pre-gyp ERR! System Darwin 16.4.0 node-pre-gyp ERR! command “/usr/local/bin/node” “/usr/local/lib/node_modules/node-inspector/node_modules/.bin/node-pre-gyp” “install” “–fallback-to-build” node-pre-gyp ERR! cwd /usr/local/lib/node_modules/node-inspector/node_modules/v8-debug node-pre-gyp ERR! node -v v7.6.0 node-pre-gyp ERR! node-pre-gyp -v v0.6.33 node-pre-gyp ERR! not ok Failed to execute ‘/usr/local/bin/node /usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js build --fallback-to-build --module=/usr/local/lib/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64/debug.node --module_name=debug --module_path=/usr/local/lib/node_modules/node-inspector/node_modules/v8-debug/build/debug/v0.7.7/node-v51-darwin-x64’ (1) /usr/local/lib └── (empty)

npm ERR! Darwin 16.4.0 npm ERR! argv “/usr/local/bin/node” “/usr/local/bin/npm” “install” “-g” “node-inspector” npm ERR! node v7.6.0 npm ERR! npm v4.2.0 npm ERR! code ELIFECYCLE npm ERR! errno 1

npm ERR! v8-debug@0.7.7 install: node-pre-gyp install --fallback-to-build npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the v8-debug@0.7.7 install script ‘node-pre-gyp install --fallback-to-build’. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the v8-debug package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! node-pre-gyp install --fallback-to-build npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs v8-debug npm ERR! Or if that isn’t available, you can get their info via: npm ERR! npm owner ls v8-debug npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request: npm ERR! /Users/jagveersingh/.npm/_logs/2017-02-23T05_40_25_485Z-debug.log

Issue Analytics

  • State:closed
  • Created 7 years ago
  • Reactions:6
  • Comments:7

github_iconTop GitHub Comments

23reactions
jessbowers-DSScommented, Feb 23, 2017

Same issue here. Try installing the latest stable release 0.7.5

npm install -g node-inspector@0.7.5
5reactions
jagsrajput21commented, Mar 29, 2017

Solved … I tried npm install -g node-inspector@0.7.5

Read more comments on GitHub >

github_iconTop Results From Across the Web

Cannot install Node Inspector - Stack Overflow
To begin with this error seems to be related with the node-gyp package. According to their documentation ...
Read more >
Installing node.js on macOS Big Sur and earlier macOS versions
Get NodeJS installed on macOS BIg Sur and earlier OSX versions. Install Node, open a node session and upgrade Node to latest version....
Read more >
node-inspector - npm
Node Inspector is a debugger interface for Node.js applications that uses the Blink Developer Tools (formerly WebKit Web Inspector).
Read more >
node-inspector | Yarn - Package Manager
Node Inspector is a debugger interface for Node.js applications that uses the Blink Developer Tools (formerly WebKit Web Inspector).
Read more >
Mac OS X 10.x &lt; 10.12.4 Multiple Vulnerabilities
(CVE-2017-2441) A flaw exists as OTR packets are not properly validated. ... Apple macOS Sierra 10.12.3 - IOFireWireFamily-null-deref FireWire Port Denial ...
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