Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
  • May 18 18:39
    mmigdol commented #137
  • Feb 25 00:22
  • Nov 21 2021 23:21
    HamishAndrew commented #1044
  • Oct 22 2021 08:10
    marcbachmann commented #976
  • Oct 22 2021 02:25
    himharsh1997 commented #976
  • Oct 22 2021 02:15
    himharsh1997 commented #976
  • Aug 24 2021 18:47
    zidingz opened #1065
  • Aug 23 2021 13:11
    khantil007 updated the wiki
  • Aug 23 2021 13:11
    khantil007 updated the wiki
  • Aug 08 2021 14:01
    MusheAbdulHakim commented #1059
  • Aug 08 2021 13:34
    MusheAbdulHakim commented #1059
  • Jul 25 2021 16:09
    sanchezzzhak commented #1031
  • Jul 25 2021 16:09
    sanchezzzhak closed #1031
  • May 28 2021 12:21
    Chieffo commented #1027
  • Apr 29 2021 16:42
    dfdeagle47 closed #941
  • Apr 29 2021 16:42
    dfdeagle47 commented #941
  • Apr 28 2021 09:12
    NikileshJayaguptha commented #1044
  • Apr 27 2021 22:09
    nerkn commented #137
  • Apr 17 2021 23:36
    miklosban updated the wiki
  • Apr 07 2021 16:47
    IgorGanapolsky commented #976
Jeff Hansen
Hi, is it possible to debug a project using babel-register with sourcemaps? If I use sourceMaps:true in the babel config, I get proper exception stack traces but inspector does not show the correct file. If I use inline sourcemaps in babel config, inspector adds .source files for each file which can be debugged, but exception stack trace line numbers point to the transpiled file.
how can i get node-inspector to play nicely with import keyword
Matt Holmes
Anyone had an issue where when using 'node-debug' to start up your debug session, you can't connect remotely to the session, but if you use node-inspector directly it works fine? I'm running my debugging session (and code) inside a Vagrant VM...node-inspector works fine stand alone, and I can connect remotely from the host to the session...but if I use 'node-debug' to start the whole thing, I can't connect remotely
Matt Holmes
Think I figured out a work around...adding "web-host": "" to my global node-inspectorrc seems to correct the issue
yep, that fixes it
probably something to do with Vagrant networking/port forwarding, I doubt it's really an NI issue per se
hey, if anyone has any remote remote , designer, DevOps or Sysadmin jobs they can post them at http://webwork.io
Nejc Vukovic
Hi when using node-inspector (MEAN Stack) with grunt debug -> why doesn’t the app stop at the breakpoint I set? Or how could I break the app to see what’s in a variable when POST request comes in?
looking for software developer in Birmingham! PM

I installed node-inspector 0.12.8 and am running node 5.6.0
When I run node-debug I get the following errors. I am now unable to debug.
I see a lot of chatter in the web about same or similar issues but have not seen any hint on how to get around this.
Hate to revert to logging to console :-)

My node-debug line looks as follows:
node-debug -d 5858 -p=5859 --nodejs --harmony app.js

Runtime.js:358 Assertion failed: Unknown experiment canvasInspectionRuntime._assert @ Runtime.js:358

InspectorBackend.js:185 Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user's experience. For more help, check https://xhr.spec.whatwg.org/

Airat Aminev
Lucas Ma
Guys, I got a problem. When debugging my code, it shows nothing on the Chrome window. What's wrong with my code?
And Chrome console has no error msgs.
Matthew Kime
@peterma did you wait? and wait some more? maybe up to 30s?
curious if there are any node-inspector maintainers here. seems like there's a broken test on master
Jeff Mealo
Has anyone attempted to debug PL/v8 (PostgreSQL embedded v8) using node-inspector or similar? It’s compatible with the d8 command line tools.

So I am using a self-made proxy to communicate between node inspector and my own script debugger. The reason is to be able to give the ability of debugging my script using node inspector (my script cannot be debugged with just any debugger as my script has its own debugger API).

Now, I am trying to get the callstack to show up. But when I log the request and response between Node inspector and the proxy, I can see that the break event happens but nothing else happens afterwards. Sometimes the "backtrace" happens after that and sometimes it does not. Callstack or scopes are not at all populated in Node Inspector. Any clues as to why that could be?

Jeff Mealo
Everyone, please help drum up support for getting debug support back into pl/v8: https://twitter.com/JeffreyMealo/status/761348871599583235
Sassafras Associated Ltd
hey all, I'm wanting to find the local variables in play on a remote server (linode) in a node/express routing, but by default it uses localhost. Would it be possible to debug the webpage running on the remote server using my local linux install at all?
the remote server has no gui, so I can't run a browser instance on the server
*node-inspector uses localhost
Junil Kim
Hi there. Is there anyone to let me know about the --inject option of node-inspector ?
What's different when enabling/disabling that option ?
I'm curious what this means "Enable injection of debugger extensions into the debugged process".
Junil Kim
@Shakyamuni177te you mean you need to debug the remote node process via node-inspector running on the host machine ?
Sassafras Associated Ltd
@sparkleholic Not quite. What I have is a host server running an express.js server process. The host server doesn't have a GUI at all, so no internet browser for testing from localhost. The server is serving publicly, however. What I want to do is to use node-inspector from the client to test from there, if that's even possible. Or... any other way around the fact I don't have browser access from the host server.
Junil Kim
hmm... these days there seems no activities at node-inspector github repo.
Utkarsh Patil

I'm installing node-inspector with npm inside an organisation with corporate proxy. I have configured the proxy settings for npm, but still the installation for nod-inspector is failing.

attaching the debug log below, please help with suggestions:
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'install',
1 verbose cli 'node-inspector',
1 verbose cli '--save',
1 verbose cli '-g' ]
2 info using npm@3.10.9
3 info using node@v4.2.4
4 silly loadCurrentTree Starting
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 silly fetchPackageMetaData node-inspector
8 silly fetchNamedPackageData node-inspector
9 silly mapToRegistry name node-inspector
10 silly mapToRegistry using default registry
11 silly mapToRegistry registry https://registry.npmjs.org/
12 silly mapToRegistry data Result {
12 silly mapToRegistry raw: 'node-inspector',
12 silly mapToRegistry scope: null,
12 silly mapToRegistry escapedName: 'node-inspector',
12 silly mapToRegistry name: 'node-inspector',
12 silly mapToRegistry rawSpec: '',
12 silly mapToRegistry spec: 'latest',
12 silly mapToRegistry type: 'tag' }
13 silly mapToRegistry uri https://registry.npmjs.org/node-inspector
14 verbose request uri https://registry.npmjs.org/node-inspector
15 verbose request no auth needed
16 info attempt registry request try #1 at 2:25:31 PM
17 verbose request using bearer token for auth
18 verbose request id c3ad1f8f54ee2ba7
19 http request GET https://registry.npmjs.org/node-inspector
20 http 200 https://registry.npmjs.org/node-inspector
21 verbose headers { server: 'CouchDB/1.5.0 (Erlang OTP/R16B03)',
21 verbose headers etag: '"BNGT0I0UB4ZBMYHKTJ3K06OTU"',
21 verbose headers 'content-type': 'application/json',
21 verbose headers 'content-encoding': 'gzip',
21 verbose headers 'cache-control': 'max-age=300',
21 verbose headers 'transfer-encoding': 'chunked',
21 verbose headers 'accept-ranges': 'bytes',
21 verbose headers date: 'Mon, 07 Nov 2016 08:55:31 GMT',
21 verbose headers via: '1.1 varnish',
21 verbose headers connection: 'close',
21 verbose headers 'x-served-by': 'cache-sin6922-SIN',
21 verbose headers 'x-cache': 'MISS',
21 verbose headers 'x-cache-hits': '0',
21 verbose headers 'x-timer': 'S1478508931.602628,VS0,VE273',
21 verbose headers vary: 'Accept-Encoding' }
22 silly get cb [ 200,
22 silly get { server: 'CouchDB/1.5.0 (Erlang OTP/R16B03)',
22 silly get etag: '"BNGT0I0UB4ZBMYHKTJ3K06OTU"',
22 silly get 'content-type': 'application/json',
22 silly get 'content-encoding': 'gzip',
22 silly get 'cache-control': 'max-age=300',
22 silly get 'transfer-encoding': 'chunked',
22 silly get 'accept-ranges': 'bytes',
22 silly get date: 'Mon, 07 Nov 2016 08:55:31 GMT',
22 silly get via: '1.1 varnish',
22 silly get connection: 'close',
22 silly get 'x-served-by': 'cache-sin6922-SIN',
22 silly get 'x-cache': 'MISS',
22 silly get 'x-cache-hits': '0',
22 silly get 'x-timer': 'S1478508931.602628,VS0,VE273',
22 silly get vary: 'Accept-Encoding' } ]
23 verbose get saving node-inspector to C:\Users\Administrator\AppData\Roaming\npm-cache\registry.npmjs.org\node-inspector.cache.json
24 verbose correctMkdir C:\Users\Administrator\AppData\Roaming\npm-cache correctMkdir not in flight; initializing
25 silly install normalizeTree
26 silly loadCurrentTree Finishing
27 silly loadIdealTree Starting
28 silly install loadIdealTree
29 silly cloneCurrentTree Starting
30 silly install cloneCurrentTreeToIdealTree
31 silly cloneCurrentTree Finishing
32 silly loadShrinkwrap Starting
33 silly install loadShrinkwrap
34 silly loadShrinkwrap Finishing
35 silly loadAllDepsIntoIdealTree Starting
36 silly install loadAllDepsIntoIdealTree
37 silly resolveWithNewModule node-inspector@0.12.8 checking installable status

38 silly cache add args [ 'node-inspector', null ]
39 verbose cache add spec node-inspector
40 silly cache add parsed spec Result {
40 silly cache add raw: 'node-inspector',
40 silly cache add scope: null,
40 silly cache add escapedName: 'node-inspector',
40 silly cache add name: 'node-inspector',
40 silly cache add rawSpec: '',
40 silly cache add spec: 'latest',
40 silly cache add type: 'tag' }
41 silly addNamed node-inspector@latest
42 verbose addNamed "latest" is being treated as a dist-tag for node-inspector
43 info addNameTag [ 'node-inspector', 'latest' ]
44 silly mapToRegistry name node-inspector
45 silly mapToRegistry using default registry
46 silly mapToRegistry registry https://registry.npmjs.org/
47 silly mapToRegistry data Result {
47 silly mapToRegistry raw: 'node-inspector',
47 silly mapToRegistry scope: null,
47 silly mapToRegistry escapedName: 'node-inspector',
47 silly mapToRegistry name: 'node-inspector',
47 silly mapToRegistry rawSpec: '',
47 silly mapToRegistry spec: 'latest',
47 silly mapToRegistry type: 'tag' }
48 silly mapToRegistry uri https://registry.npmjs.org/node-inspector
49 verbose addNameTag registry:https://registry.npmjs.org/node-inspector not in flight; fetching
50 verbose get https://registry.npmjs.org/node-inspector not expired, no request
51 silly addNameTag next cb for node-inspector with tag latest
52 silly addNamed node-inspector@0.12.8
53 verbose addNamed "0.12.8" is a plain semver version for node-inspector
54 silly mapToRegistry name node-inspector
55 silly mapToRegistry using default registry
56 silly mapToRegistry registry https://registry.npmjs.org/
57 silly mapToRegistry data Result {
57 silly mapToRegistry raw: 'node-inspector',
57 silly mapToRegistry scope: null,
57 silly mapToRegistry escapedName: 'node-inspector',
57 silly mapToRegistry name: 'node-inspector',
57 silly mapToRegistry rawSpec: '',
57 silly mapToRegistry spec: 'latest',
57 silly mapToRegistry type: 'tag' }
58 silly mapToRegistry uri https://registry.npmjs.org/node-inspector
59 verbose addRemoteTarball https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz not in flight; adding
60 verbose addRemoteTarball [ 'https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz',
60 verbose addRemoteTarball 'a59c3dc47cb08d15a2e526be3a1da7d64e5c227f' ]
61 info retry fetch attempt 1 at 2:25:32 PM
62 info attempt registry request try #1 at 2:25:32 PM
63 http fetch GET https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
64 verbose request using bearer token for auth
65 http fetch 503 https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
66 info retry will retry, error on last attempt: Error: server error 503
67 info attempt registry request try #2 at 2:25:43 PM
68 http fetch GET https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
69 verbose request using bearer token for auth
70 http fetch 503 https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
71 info retry will retry, error on last attempt: Error: server error 503
72 info attempt registry request try #3 at 2:26:44 PM
73 http fetch GET https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
74 verbose request using bearer token for auth
75 http fetch 503 https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
76 error fetch failed https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
77 warn retry will retry, error on last attempt: Error: fetch failed with status code 503
78 info retry fetch attempt 2 at 2:26:55 PM
79 info attempt registry request try #1 at 2:26:55 PM
80 http fetch GET https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
81 verbose request using bearer token for auth
82 http fetch 503 https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
83 info retry will retry, error on last attempt: Error: server error 503
84 info attempt registry request try #2 at 2:27:06 PM
85 http fetch GET https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
86 verbose request using bearer token for auth
87 http fetch 503 https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
88 info retry will retry, error on last attempt: Error: server error 503
89 info attempt registry request try #3 at 2:28:07 PM
90 http fetch GET https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
91 verbose request using bearer token for auth
92 http fetch 503 https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
93 error fetch failed https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
94 warn retry will retry, error on last attempt: Error: fetch failed with status code 503
95 info retry fetch attempt 3 at 2:29:07 PM
96 info attempt registry request try #1 at 2:29:07 PM
97 http fetch GET https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
98 verbose request using bearer token for auth
99 http fetch 503 https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
100 info retry will retry, error on last attempt: Error: server error 503
101 info attempt registry request try #2 at 2:29:18 PM
102 http fetch GET https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
103 verbose request using bearer token for auth
104 http fetch 503 https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
105 info retry will retry, error on last attempt: Error: server error 503
106 info attempt registry request try #3 at 2:30:19 PM
107 http fetch GET https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
108 verbose request using bearer token for auth
109 http fetch 503 https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
110 error fetch failed https://registry.npmjs.org/node-inspector/-/node-inspector-0.12.8.tgz
111 silly rollbackFailedOptional Starting
112 silly rollbackFailedOptional Finishing
113 silly runTopLevelLifecycles Finishing
114 silly install printInstalled
115 verbose stack Error: fetch failed with status code 503
115 verbose stack at Request.<anonymous> (C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\node_modules\npm-registry-client\lib\fetch.js:51:14)
115 verbose stack at emitOne (events.js:77:13)
115 verbose stack at Request.emit (events.js:169:7)
115 verbose stack at Request.onRequestResponse (C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\node_modules\request\request.js:954:10)
115 verbose stack at emitOne (events.js:77:13)
115 verbose stack at ClientRequest.emit (events.js:169:7)
115 verbose stack at HTTPParser.parserOnIncomingClient [as onIncoming] (_http_client.js:415:21)
115 verbose stack at HTTPParser.parserOnHeadersComplete (_http_common.js:88:23)
115 verbose stack at TLSSocket.socketOnData (_http_client.js:305:20)
115 verbose stack at emitOne (events.js:77:13)
116 verbose cwd C:\Users\Administrator\workspace\nodeapp\Demo_Node_Inspector
117 error Windows_NT 6.1.7601
118 error argv "C:\Program Files\nodejs\node.exe" "C:\Users\Administrator\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js" "install" "node-inspector" "--save" "-g"
119 error node v4.2.4
120 error npm v3.10.9
121 error fetch failed with status code 503
122 error If you need help, you may report this error at:
122 error https://github.com/npm/npm/issues
123 verbose exit [ 1, true ]
hi, anybody managed to make it work on alpine ?
or maybe the problem is node 7.4
the same problem
v8-debug@0.7.7 preinstall /usr/local/lib/node_modules/.staging/v8-debug-5be573b2
> node -e 'process.exit(0)'
> v8-profiler@5.6.5 preinstall /usr/local/lib/node_modules/.staging/v8-profiler-4971d27a
> node -e 'process.exit(0)'
/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.4.0 (node-v51 ABI) (falling back to source compile with node-gyp)
Arti Villa
anyone else having issues installing node-inspector globally on node v7?
Hey guys, node-inspector@1.0.0 has been released and I think most of the issues should be resolved now.
Jack Murphy
Hi folks, working with TypeScript and having some trouble with source maps: https://stackoverflow.com/questions/46307661/how-do-i-get-typescript-source-files-to-show-up-in-node-inspector
6796 verbose stack Error: v8-debug@1.0.1 install: node-pre-gyp install --fallback-to-build
6796 verbose stack Exit status 1
6796 verbose stack at EventEmitter.<anonymous> (d:\node\node_modules\npm\node_modules\npm-lifecycle\index.js:285:16)
6796 verbose stack at EventEmitter.emit (events.js:182:13)
6796 verbose stack at ChildProcess.<anonymous> (d:\node\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
6796 verbose stack at ChildProcess.emit (events.js:182:13)
6796 verbose stack at maybeClose (internal/child_process.js:947:16)
6796 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:236:5)
6797 verbose pkgid v8-debug@1.0.1
6798 verbose cwd D:\C_Disk\ksana2015\myHTTPServer
6799 verbose Windows_NT 10.0.17134
6800 verbose argv "d:\node\node.exe" "d:\node\node_modules\npm\bin\npm-cli.js" "install" "-g" "node-inspector"
6801 verbose node v10.0.0
6802 verbose npm v5.6.0
6803 error code ELIFECYCLE
6804 error errno 1
6805 error v8-debug@1.0.1 install: node-pre-gyp install --fallback-to-build
6805 error Exit status 1
6806 error Failed at the v8-debug@1.0.1 install script.
On my win10, I just could'nt "npm install -g node-inspector"! Could some one help?
Álvaro Arcaya
Like console as admin
David Napier
Also having issues installing node-inspector on OS X or Arch Linux.
Hello!!; im having issues trying to install/run node-debugger interface for node --inspector in atom, do you know of any atom plugin to integrate node inspector?. Anyway i would like to help on other bugs, cheers.
Nicolás Narváez
(Ghost = me)
every time :(
I have difficulty on installing node inspector on windows10
need to install it in order to cage my port from 8080 to 8089