Cannot find module '_debugger'

Question

Cannot find module '_debugger'

billgertz opened this issue 6 years ago · comments

Start Atom
Pops up at startup:

Error: Cannot find module '_debugger'
    at Module._resolveFilename (module.js:543:15)
    at Module._resolveFilename (/Applications/Development/Atom.app/Contents/Resources/electron.asar/common/reset-search-paths.js:35:12)
    at Function.get_Module._resolveFilename (/Applications/Development/Atom.app/Contents/Resources/app/src/module-cache.js:354:58)
    at Module.require (file:///Applications/Development/Atom.app/Contents/Resources/app.asar/static/index.js:40:43)
    at require (/Applications/Development/Atom.app/Contents/Resources/app/src/native-compile-cache.js:66:33)
    at Object.<anonymous> (/Users/bgertz/.atom/packages/node-debugger/lib/debugger.coffee:5:12)
    at Object.<anonymous> (/Users/bgertz/.atom/packages/node-debugger/lib/debugger.coffee:1:1)
    at Object.<anonymous> (/Users/bgertz/.atom/packages/node-debugger/lib/debugger.coffee:1:1)
    at Module.get_Module._compile (/Applications/Development/Atom.app/Contents/Resources/app/src/native-compile-cache.js:106:36)
    at Object.value [as .coffee] (/Applications/Development/Atom.app/Contents/Resources/app/src/compile-cache.js:240:29)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:504:12)
    at Function.Module._load (module.js:496:3)
    at Module.require (file:///Applications/Development/Atom.app/Contents/Resources/app.asar/static/index.js:47:45)
    at require (/Applications/Development/Atom.app/Contents/Resources/app/src/native-compile-cache.js:66:33)
    at Object.<anonymous> (/Users/bgertz/.atom/packages/node-debugger/lib/node-debugger.coffee:2:14)
    at Object.<anonymous> (/Users/bgertz/.atom/packages/node-debugger/lib/node-debugger.coffee:1:1)
    at Object.<anonymous> (/Users/bgertz/.atom/packages/node-debugger/lib/node-debugger.coffee:1:1)
    at Module.get_Module._compile (/Applications/Development/Atom.app/Contents/Resources/app/src/native-compile-cache.js:106:36)
    at Object.value [as .coffee] (/Applications/Development/Atom.app/Contents/Resources/app/src/compile-cache.js:240:29)
    at Module.load (module.js:561:32)
    at tryModuleLoad (module.js:504:12)
    at Function.Module._load (module.js:496:3)
    at Module.require (file:///Applications/Development/Atom.app/Contents/Resources/app.asar/static/index.js:47:45)
    at require (internal/module.js:11:18)
    at customRequire (/Applications/Development/Atom.app/Contents/Resources/app/static/<embedded>:96:26)
    at Package.requireMainModule (/Applications/Development/Atom.app/Contents/Resources/app/src/package.js:782:33)
    at Package.activateNow (/Applications/Development/Atom.app/Contents/Resources/app/src/package.js:220:40)
    at measure (/Applications/Development/Atom.app/Contents/Resources/app/src/package.js:206:33)
    at Package.measure (/Applications/Development/Atom.app/Contents/Resources/app/src/package.js:88:25)
    at activationPromise.Promise (/Applications/Development/Atom.app/Contents/Resources/app/src/package.js:200:20)
    at new Promise (<anonymous>)
    at Package.activate (/Applications/Development/Atom.app/Contents/Resources/app/src/package.js:198:38)
    at PackageManager.activatePackage (/Applications/Development/Atom.app/Contents/Resources/app/src/package-manager.js:695:42)
    at config.transactAsync (/Applications/Development/Atom.app/Contents/Resources/app/src/package-manager.js:670:36)
    at Config.transactAsync (/Applications/Development/Atom.app/Contents/Resources/app/src/config.js:866:28)

Jonathan Montgomery · Answer 1 · Fri Jul 20 2018 09:32:03 GMT+0800 (China Standard Time)

Seems like the _debugger module was removed from node in v8 nodejs/node@90476ac6ee

Owen Dall Sotomayor · Answer 2 · Fri Aug 10 2018 01:33:01 GMT+0800 (China Standard Time)

I still get this every time I open Atom...

Robin Rosenstock · Answer 3 · Thu Aug 16 2018 16:25:10 GMT+0800 (China Standard Time)

Duplicate of #261 and #259

Jade · Answer 4 · Fri Sep 21 2018 08:10:12 GMT+0800 (China Standard Time)

got this problem too

Vijendra Kulhade · Answer 5 · Wed Sep 26 2018 02:06:03 GMT+0800 (China Standard Time)

same problem. Is there any workaround??

Zach Caceres · Answer 6 · Sat Jan 05 2019 15:10:49 GMT+0800 (China Standard Time)

same, any solution?

Oscar-Deng · Answer 7 · Sun Feb 03 2019 18:29:20 GMT+0800 (China Standard Time)

same, solution? anybody solved?

Rankyn · Answer 8 · Mon Mar 04 2019 05:20:03 GMT+0800 (China Standard Time)

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.

Pysis · Answer 9 · Wed Mar 20 2019 22:21:03 GMT+0800 (China Standard Time)

Just redirect to this from the Atom error reporter that simply suggests uninstalling this package: #266

Folât Pjêrsômêj · Answer 10 · Wed Jul 10 2019 23:07:46 GMT+0800 (China Standard Time)

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

Pysis · Answer 11 · Sun Dec 27 2020 03:01:17 GMT+0800 (China Standard Time)

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.