6 ms·
I believe the comparison was not with text-based debuggers, but with the more mainstream Node.js debugging options that also provide Blink or Chrome DevTools UI
by hallmark 10y ago
I believe the comparison was not with text-based debuggers, but with the more mainstream Node.js debugging options that also provide Blink or Chrome DevTools UIs:
1. Node Inspector (https://github.com/node-inspector/node-inspector https://github.com/node-inspector/node-inspector), the most prevalent Node.js debugging tool, at least until Node v6.3.0. And which also happens to be mentioned by Jam3/devtool in the Comparisons section.
2. Built-in Chrome DevTools debugging support as of node v6.3.0 (https://medium.com/@paul_irish/debugging-node-js-nightlies-with-chrome-devtools-7c4a1b95ae27#.knjnbsp6t https://medium.com/@paul_irish/debugging-node-js-nightlies-w...). Simply by running:
> node --inspect foo.js
- alistproducer2 10y agoThanks for pointing these out. I tried using the --inspect flag like your article pointed out but I couldn't get it to work with Chrome 54. I can't really give a compare and contrast between what I'm using and the --inspect flag. From the article, I feel like I'd like --inspect better if I could get it to work.