Refs: microsoft/vscode-js-debug#703

• macOS @isidorn
• linux @joaomoreno
• windows @eamodio

Complexity: 5

Create Issue

This month we brought js-debug auto attach back. This includes some behavior changes:

• You can now configure whether js-debug auto attach will be used via the debug.javascript.usePreviewAutoAttach setting. (defaults to true)
• By default, auto attach will connect to 'user' node scripts and common tools. It does this by not attaching to any script running in a node_modules, excluding some common tools like mocha, ts-node, etc.
  • The "common tools" and scripts is configurable in debug.javascript.autoAttachSmartPattern
  • The attachment mode is configurable debug.javascript.autoAttachFilter
  • Verify this functionality works and makes sense to you.
• Auto attach happens through environment variables which are persisted per-workspace.
  • Toggle attach between different settings and move around workspaces. Verify that the correct state is reflected in each workspace.
  • You can verify that auto attach is fully 'disabled' by checking that echo $NODE_OPTIONS / echo $env:NODE_OPTIONS is not present
• There are changes around when we decide we can enable auto attach. Primarily, we cannot verify the user is running Node 12 and there's a space in the workspace storage folder, auto attach will not be enabled and we'll show a nag warning.

Additional ask: please leave auto attach "On" or "Off" (not disabled) for the remainder of endgame as you go about your business, and let me know if you run into any issues using the terminal or running node scripts.