question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

node debug is broken for che-theia:next

See original GitHub issue

Describe the bug

The debug session type “node” is not supported.

Che version

  • latest
  • nightly
  • other: please specify

Steps to reproduce

  1. Create new application with node from stack ‘NodeJS Express Web Application’
  2. Run application with enabled debugger: task with name run the web app (debugging enabled)
  3. Open debug panel select ‘Attach to remote’ debug config and click on run button:

Actual result: an error: The debug session type “node” is not supported.

Expected behavior

Debugger should attach to the application using remote debug protocol. I assume that for che-theia:7.9.1 debugger forks fine, but for che-theia:next it doesn’t work.

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)

Screenshots

Installation method

  • chectl
  • che-operator
  • minishift-addon
  • I don’t know

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: please specify

Eclipse Che Logs

Additional context

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:11 (11 by maintainers)

github_iconTop GitHub Comments

1reaction
tolushacommented, Mar 18, 2020

I would say there are two options:

  1. change debug types to node2 (it is needed to check)
  2. add vsix extension [1] to [2]

[1] https://marketplace.visualstudio.com/items?itemName=ms-vscode.node-debug [2] https://github.com/eclipse/che-plugin-registry/blob/master/v3/plugins/ms-vscode/node-debug2/1.33.0/meta.yaml

0reactions
ericwillcommented, May 4, 2020

This has been fixed with #16728.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Can't get node-debug to work - Stack Overflow
Now I have a lovely browser window open showing me my code with breakpoints... and no idea which url to use to actually...
Read more >
Debug Node.js Apps using Visual Studio Code
The Visual Studio Code editor includes Node.js debugging support. Set breakpoints, step-in, inspect variables and more.
Read more >
Running and debugging Node.js | PyCharm Documentation
PyCharm helps you run and debug your Node.js applications. You can debug applications that are started from PyCharm as well as attach to ......
Read more >
Debugger | Node.js v19.3.0 Documentation
Node.js includes a command-line debugging utility. The Node.js debugger client is not a full-featured debugger, but simple stepping and inspection are ...
Read more >
Debugging in WebStorm broke after new update (#WS ...
Recreated, logged as WEB-37804. Please follow this ticket for updates. As a workaround, please try disabling js.debugger.use.node.options ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found