NodeJS "--debug" parameter is deprecated

Question

NodeJS "--debug" parameter is deprecated

Opened this issue 8 years ago · 19 comments

(node:2624) DeprecationWarning: node --debug is deprecated. Please use node --inspect instead.

skywinder commented 7 years ago

+1 on Mac

dhowe commented 6 years ago

Status??

Answer 1 · 2017-07-06T08:47:50.000Z

Ran into the same problem today.

Answer 2 · 2017-07-14T07:18:52.000Z

DeprecationWarning: node --debug and node --debug-brk are invalid. Please use node --inspect or node --inspect-brk instead.

Answer 3 · 2017-07-24T14:15:12.000Z

same here , never used this, but fixing the path , this is what I get, hard first run !

Answer 4 · 2017-08-02T18:03:31.000Z

Can any of you get the debugger to work with Node 6.11? Even using --inspect, I can do breakpoints, but I cannot inspect any variables, as reported in issue #237

Answer 5 · 2017-08-09T13:11:23.000Z

I'm using node v8.2.1 having the same prob.
maybe line 56 in debugger.coffee needs to change to "--inspect-brk"? perhaps it shouldn't be hard coded in a future release :-)

Answer 6 · 2017-08-11T14:05:39.000Z

I think it isn't that simple. Otherwise I'd be able to inspect values when changing the command line manually.

Answer 7 · 2017-08-29T12:58:54.000Z

So the package is node v8 incompatible? Any news on this?

Answer 8 · 2017-09-11T03:48:05.000Z

Yep I have the same issue. I tried changing line 56 but after reloading the app, it only loads up in chrome. I can't debug from within Atom using node 8 on osx.

Answer 9 · 2017-10-30T22:10:13.000Z

Hi adding in a +1 on the issue and looking for a solution. I am new to Mac and Atom (new Job) so not sure how much I can add at this point other than I would like to be able to debug node 8 in atom. Any information (such as why this is an issue) would be appreciated. It is deeper than the command line option - right?

Answer 10 · 2017-12-14T12:41:05.000Z

Facing same issue !! Please share if anyone got solution .

Answer 11 · 2018-02-13T08:30:24.000Z

+1 on Mac using v8.9.3

Answer 12 · 2018-02-20T02:40:09.000Z

+1 on Windows, using v8.9.3
Anyone found a solution?

Answer 13 · 2018-02-21T01:43:08.000Z

So, one way to solve it, as @vildmedtog pointed out.

Go to your .atom directory, find packages\node-debugger\lib\debugger.coffee line 56, change --debug to --inspect.

~~That solved the issue for me.~~

Edit:
This makes the error go away, but I don't seem to get the debugger itself working, I assume this is because the node-inspector uses Chrome websocket debugger, not the old debugging method.
I suppose we'll need a new version of node-debugger after all.

Edit 2018-06-17:
Not sure if this type of comments is welcome here, but this is a personal opinion, VSCode gives a much better debugging experience, and a generally better editing experience, it probably would be a good idea to use it until this is fixed.

Answer 14 · 2018-04-11T17:45:09.000Z

Same issue here. No fix still?

Answer 15 · 2018-04-11T23:05:34.000Z

@relief-melone Since I couldn't debug node 8 in atom, I use vscode and chrome dev tools now.

Answer 16 · 2018-04-16T14:38:41.000Z

+1 on ubuntu 16.04 and Node v8

Answer 17 · 2018-05-11T02:46:47.000Z

Any status on a fix? This issue renders the whole package worthless.