[Feature] Auto-connect the debugger when a target becomes available

[robertrossmann]

Description

The current debugger (for Node.js, specifically), requires manual action to connect to a running process (via Attach debugger dialog window).

A major improvement would be to add a configuration checkbox to automatically attach to a running Node.js process when it becomes available and the debugger pane is open.

A similar behaviour already exists in the Chrome's Dedicated devtools for Node window which auto-connects to any running inspectable Node.js process.

Expected Behavior

When the debugger pane is open and a hypothetical new option auto-connect is checked, and a new Node.js process with the --inspect or --inspect-brk flag is started on a known or previously-configured port (9229 by default), the Debugger for Atom should automatically start the debugging session.

Actual Behavior

I have to start the Node.js process with the --inspect-brk and then in Atom, invoke the Attach debugger dialog window and click Attach to actually start the debugging session.

Versions

• Atom: 1.27.0-beta.1
• Client OS: macOS 10.13.4
• atom-ide-ui: 0.11.2

Additional Details

Installed Packages

├── [email protected] (disabled)
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] (disabled)
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] (disabled)
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected] (disabled)
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
├── [email protected]
└── [email protected]