node --expose_debug_as=v8debug gives "bade option"

Created on 2 Jun 2017  路  4Comments  路  Source: nodejs/node

  • Version: 8.0.0
  • Platform: 64-bit (Windows)
  • Subsystem:


Hi i just updated to node v8.0.0 and now im can't start the debugger anymore.

To reproduce just enter the following on your cmd or shell:

node --expose_debug_as=v8debug
Program Files\nodejs\node.exe: bad option: --expose_debug_as=v8debug

with v7.10.0 this isn't a problem.

V8 Engine debugger question

Most helpful comment

Got here trying to run debug on node v8 in WebStorm.
It worked for me after adding --inspect to node parameters as stated here:
https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000397470-Debugging-node-version-8-1-2

All 4 comments

8.x no longer has the "debugger" (it has been deleted from v8), it has the "inspector", so this functionality is gone as is the CLI to expose it.

Consider using the inspector: https://nodejs.org/api/inspector.html

/cc @ofrobots @eugeneo

You can use this instead.

const vm = require('vm');
const v8debug = vm.runInDebugContext('Debug');

Note that vm.runInDebugContext is going away soon too, and your best bet would be to move the the inspector API as @sam-github mentioned.

Thanks a lot.

Got here trying to run debug on node v8 in WebStorm.
It worked for me after adding --inspect to node parameters as stated here:
https://intellij-support.jetbrains.com/hc/en-us/community/posts/115000397470-Debugging-node-version-8-1-2

Was this page helpful?
0 / 5 - 0 ratings

Related issues

stevenvachon picture stevenvachon  路  3Comments

vsemozhetbyt picture vsemozhetbyt  路  3Comments

addaleax picture addaleax  路  3Comments

Brekmister picture Brekmister  路  3Comments

akdor1154 picture akdor1154  路  3Comments