Open billgertz opened 5 years ago
Seems like the _debugger module was removed from node in v8 https://github.com/nodejs/node/commit/90476ac6ee
I still get this every time I open Atom...
Duplicate of #261 and #259
got this problem too
same problem. Is there any workaround??
same, any solution?
same, solution? anybody solved?
There does not seem to be a solution to this issue, or support for the package. Someone else suggested using atonm-ide-debgger-node, but that package is not intuitive, and does not have a list of commands.
Just redirect to this from the Atom error reporter that simply suggests uninstalling this package: https://github.com/kiddkai/atom-node-debugger/issues/266
Yes, but it suggests to get rid of Atom and I love atom.
So the trick is to find a working nodejs-debugger:
apm uninstall node-debugger
apm install xatom-debug xatom-ui xatom-syntax
I certainly want to use some solution for Atom, but there seem to be a lot of old, out-dated, or broken articles or packages.
This xatom stuff seems to be pretty good adding UI to Atom, although all that exist now are xatom-debug
and xatom-debug-nodejs
that I used for my exercise. It did give me information and correct breakpointing, but I receive the error "XAtom Debug: Unable to map file" that I have found at these links:
Although I'm not trying to do anything remote, just a local fs script as I can describe in that issue link..
Just want to find a decent debugging solution for NodeJS projects and Atom, or at least through the CLI. So many old or broken articles, programs and such like node-debug
, node-debugger
, node-inspect
, node-inspector
, atom-ide-debugger-node
, and now this xatom-
one. Wanted to keep it simple to inside Atom or on CLI to keep development fast outside of the Chrome DevTools connection, although that is nice to use.