Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unable to connect to node #556

Open
titaniumbones opened this issue Feb 9, 2022 · 0 comments
Open

unable to connect to node #556

titaniumbones opened this issue Feb 9, 2022 · 0 comments

Comments

@titaniumbones
Copy link

I am unable to get dap-mode working with node or firefox. Chrome debugging works, but is significantly more complex to configure than indicated in the documentation.

I suspect the firefox issue will be difficult to track down. Steps to reproduce existing node.js issues:

Warning (emacs): Initialize request failed: Attribute 'program' is not absolute ('{path}'); consider adding '${workspaceFolder}/' as a prefix to make it absolute. Disable showing Disable logging
  • self-written node config in launch.json with the following content:
{
    "name": "NODE: loop.js",
    "type": "node",
    "outfiles": ["*.js"],
    "runtime": "/home/matt/.fnm/aliases/default/bin/node",
    "program": "/home/matt/.emacs.d/.extension/vscode/ms-vscode.node-debug2/extension/out/src/nodeDebug.js",
    "request": "launch",
    "file": "${workspaceFolder}/loop.js"
  }

this launches but crashes immediately before debugging any code with a "module not found" error (stack seems to be hard to copy, my apologies)

I feel myself to be shooting in the dark here and would love to hear if others able to make this work. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant