Debugging

[hacki11]

Is your feature request related to a problem? Please describe.
Would be great to be able to debug directly in VS Code to avoid switching between VS Code and the Adapters IDE.

Describe the solution you'd like
Are there already ideas or thoughts about this? With the Remote Development feature of VS Code to connect to a machine via SSH i could imagine that it would be easier now to attach to a node process. Can we collect the missing pieces needed?

Describe alternatives you've considered

Additional context

[nokxs]

I think it would be great, if the Extension could support debugging.

I have never used the debugging Feature im the web IDE, so I have no clue how it is working. I will investigate how it is working and I will try to reverse engineer it, but I don't know when this will happen.

If you have any resources in how to get started on this topic, it might speed up the development.

[nokxs]

Real VS Code debugging for ioBroker is theoretically possible, but not easy to implement in this extension.

What would be required:

1. Adapter-side support: the javascript adapter must be startable in Node inspect mode (per instance, stable port).
2. Instance lifecycle control from the extension: enable debug mode, restart the adapter instance, wait until it is alive again.
3. VS Code debug integration: add a debug command/config provider that orchestrates upload + start + attach.
4. Reliable source mapping: breakpoints must map consistently to local script files.
5. Docker/network handling: make the inspect port reachable from VS Code (or use SSH tunnel), including firewall/port mapping.
6. UX and error handling: clear guidance for unreachable ports, wrong instance, port conflicts, and missing permissions.

Conclusion: not impossible, but significantly hard to achieve reliably.

For this reason, this ticket will be closed.