adapter-development

Build debug adapters using a component-based architecture with ProcessManager, PortManager, LaunchOrchestrator, and TargetResolver. Follow language-specific patterns for debugpy (Python), vscode-js-debug (JavaScript), and java-debug (Java) to handle launching, breakpoints, and source path resolution across local and remote scenarios.

Use modular base components (ProcessManager, PortManager, LaunchOrchestrator, TargetResolver, SourcePathResolver, LifecycleHooks) with environment hooks and resource cleanup. This framework delegates responsibilities cleanly, scales across languages, and handles port lifecycle and process management consistently.

Implement PortManager for allocation and LifecycleHooks for cleanup to prevent port conflicts and orphaned processes. The adapter orchestrates launch sequences via LaunchOrchestrator while maintaining process state, enabling reliable local and remote debugging.

Yes. The component-based framework provides reusable patterns for each language (debugpy, vscode-js-debug, java-debug), but language-specific configurations and hooks adapt behavior for each runtime's debugging protocol, breakpoint handling, and source path requirements.

SourcePathResolver validates and maps file paths; TargetResolver identifies debug targets. If resolution fails, check environment validation, launch configuration, and per-language path mapping rules. The documented patterns include troubleshooting for each supported language.

Yes. Use environment hooks and validation checks to verify runtime availability, paths, and dependencies before LaunchOrchestrator starts the debugger. Proper setup prevents launch failures and ensures breakpoints and source paths resolve correctly across local and remote targets.