Node: Node v 8: bad option: --expose_debug_as=v8debug

[lukaszewczak]

Hi,
After update to node v 8, it is not possible to debug npm script in Webstorm because of error bad option: --expose_debug_as=v8debug. It worked under node v 6.

• Version: v8.1.0
• Platform: Windows 10 (64-bit)
• Subsystem:

`"C:\Program Files (x86)\JetBrains\WebStorm 2017.1\bin\runnerw.exe" "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" run debug --scripts-prepend-node-path=auto

node %NODE_DEBUG_OPTION% app.js

node: bad option: --expose_debug_as=v8debug
npm ERR! code ELIFECYCLE
npm ERR! errno 9
npm ERR! [email protected] debug: node %NODE_DEBUG_OPTION% app.js
npm ERR! Exit status 9
npm ERR!
npm ERR! Failed at the [email protected] debug 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\Dom\AppData\Roaming\npm-cache_logs\2017-06-08T23_19_05_593Z-debug.log

Process finished with exit code 9`

[eugeneo]

V8 debugger API had been superseded by the V8 inspector API. If you depend on a module that relies on it you should open a bug against that module.

[sam-github]

duplicate, see https://github.com/nodejs/node/issues/13410 for workarounds

[refack]

@lukaszewczak sorry we couldn't do more, but you should check the WebStorm site, they have information about how to work with the new inspector protocol https://www.jetbrains.com/help/webstorm/run-debug-configuration-node-js.html?search=node

[lukaszewczak]

Thank you all for the information.

[matthewmorgan]

FYI for anyone who finds this thread, Webstorm 2017.2 will debug with Node 8

[packetstracer]

adding --inspect value in node parameters worked for me

Link to intellij support post

[mwojtera]

@packetstracer url is badly linked. this works -> https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000397470/comments/115000392244

Still a great find, saved me a lot of work, thank you