Nodejs 8 (node:4376) [DEP0062] DeprecationWarning: node --debug and node --debug-brk are invalid. Please use node --inspect or node --inspect-brk instead.

[paulvi]

Initially raised as Nodeclipse/www.nodeclipse.org#77

It seems that Nodejs 8 change option names

(node:4376) [DEP0062] DeprecationWarning: node --debug and node --debug-brk are invalid. Please use node --inspect or node --inspect-brk instead.

The line in question is https://github.com/Nodeclipse/nodeclipse-1/blob/master/org.nodeclipse.debug/src/org/nodeclipse/debug/launch/LaunchConfigurationDelegate.java#L114

cmdLine.add("--debug"+brk+"="+nodeDebugPort);

i.e. using --debug is hard-coded now

TODO test with Node.js 8, if using --inspect would work.

HELP WANTED!!

[dmidge8]

I still have the same issue, that I found through issue #107 .
"Nodeclipse/chromedevtools failed to connect to Standalone V8 VM ( Check Help (F1) and Support http://www.nodeclipse.org/#support )
. Info:
Connexion refusée (Connection refused)"

I am using nodeclipse 1.0.2, which seems to be the latest version. Is the fix included in this version?

[1fifoto]

I could really use this. Is there anything I can do to help?

[paulvi]

yes, change https://github.com/Nodeclipse/nodeclipse-1/blob/master/org.nodeclipse.debug/src/org/nodeclipse/debug/launch/LaunchConfigurationDelegate.java#L114

build, try that everything works fine

then I will release or help to release

[paulvi]

Also need to know at what Node.js version this option where renamed,
and do logic to support newer and older versions

[tyllastarr]

I am having the issue with Node.js v8.11.3. Haven't tested with Node.js 10 yet, but I plan to later.

[Fr33dan]

Unfortunately it's not a renamed option but a completely new replacement. According to the Node.js V6 change log the --inspect option was added in 6.3.0 to use the "inspector protocol" as an experimental feature which is different than the debugger protocol. Then the V8 changelog says:

• The --debug command-line argument has been deprecated. Note that
  using --debug will enable the new Inspector-based debug protocol
  as the legacy Debugger protocol previously used by Node.js has been
  removed. [010f864426]
  #12949.

So the issue is not that the the VM failed to launch because of the changed option, but that the debugger can't connect to the VM because the protocol has changed.

I did go ahead and changing the option in LaunchConfigurationDelegate.java which made the depreciation warning go away, but it still thinks the VM failed to launch.