Node v8.0.0 Released

Re:Node v8.0.0 Released by cheapsteak on Tuesday May 30, 2017 @03:39PM (#14447908)

>node-inspect has been integrated directly into the Node.js runtime

Is node-inspect the same thing as node-inspector or something else?

[ Parent | on HN ]

Re:Node v8.0.0 Released by jkrems on Tuesday May 30, 2017 @03:48PM (#14447987)

Disclaimer: Author of `node-inspect`

No, `node inspect` is the new command line debugger for `node --inspect` which replaces `node debug` for `node --debug`. The name is derived from `node --inspect` and has no relation to `node-inspector`.

[ Parent | on HN ]

Re:Node v8.0.0 Released by nulagrithom on Tuesday May 30, 2017 @03:59PM (#14448076)

Thanks for your work! CLI has always been my primary method of debugging node, and I'd hate to see it go away.

Is this pretty much identical to the old debugger?

[ Parent | on HN ]

Re:Node v8.0.0 Released by jkrems on Wednesday May 31, 2017 @01:24PM (#14454269)

Yep, the same commands should still work. There's some additional commands now for CPU/memory profiles. But that's the biggest difference - hopefully.

[ Parent | on HN ]

Re:Node v8.0.0 Released by AngelloPozo on Tuesday May 30, 2017 @03:41PM (#14447925)

when you run something you, can add the --inspect flag to debug.

1. node --inspect app.js 2. In chrome do `about:inspect`

you now have debugger attached. WIN!

[ Parent | on HN ]