Debugging nodejs projects seems to be impossible

[amisevsk]

Describe the bug

Debugging the sample projects included in the NodeJS Angular, Mongo, and React devfiles seems to not be possible currently.

I was able to work around these issues for the simple Node Express devfile but cannot figure it out for the others.

Che version

• latest
• nightly
• other: please specify

Steps to reproduce

Start e.g. the NodeJS Angular devfile in Che and attempt to debug.

Expected behavior

It is clear how to debug the application, or clear that debugging is not possible for some reason.

Runtime

• kubernetes (include output of kubectl version)
• Openshift (include output of oc version)
• minikube (include output of minikube version and kubectl version)
• minishift (include output of minishift version and oc version)
• docker-desktop + K8S (include output of docker version and kubectl version)
• other: (please specify)

[benoitf]

@amisevsk is area is che-theia or che-languages ?

I mean, the issue that you're facing is how to see breakpoints menu, etc or that you're not able to use the typescript debugger ?

[amisevsk]

@benoitf The issue is that connecting a debugger to the application is impossible; none of the options in Theia work. As far as I understand, the nodejs debug configurations come built-in to Theia, but I'm not sure what the best area is for this, it's likely a combination of a devfile issue and a debugger issue.

As a user, I could not get debugging to work in those three devfiles.

[tsmaeder]

@amisevsk trying to find out what you're doing exatly, here: are you using a launching configuration or are you running the application in the dev or runtime container and trying to do remote debugging?

[amisevsk]

@tsmaeder It has been awhile and I know the Theia side has reworked the nodejs debugging options, but I tried every debug config autocompletion and could not get it to work. I haven't tested in a month though, so it may be resolved -- I'll double check when I have a moment.

[che-bot]

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.