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

'${workspaceFolder}' can not be resolved in a multi folder workspace - While using Node JS auto attach debugger #103099

Closed
ep1cman opened this issue Jul 22, 2020 · 7 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Milestone

Comments

@ep1cman
Copy link

ep1cman commented Jul 22, 2020

  • VSCode Version: 1.47
  • OS Version: Mac OS 10.15.5

Looks like there has been a a regression and the issue occurs again with the latest release
See here: #94725
Downgrading to 1.46 fixes and it works as expected

@ep1cman ep1cman changed the title '${workspaceFolder}' can not be resolved in a multi folder workspace '${workspaceFolder}' can not be resolved in a multi folder workspace - While using Node JS auto attach debugger Jul 22, 2020
@AskAlice
Copy link

I'm getting this. Probably related to ms-vscode.node-debug as seen in #94725

@joscarras
Copy link

Same here with 1.47.2

@AskAlice
Copy link

AskAlice commented Jul 28, 2020

switch your type to pwa-node,. That seems to fix it, though there are some configuration quirks that don't seem to translate over

@ep1cman
Copy link
Author

ep1cman commented Jul 28, 2020

How do I set that for the auto attach debugger? I use to be able just run commands in the built in terminal rather than via launch.json and it would allow me to debug.

@AskAlice
Copy link

AskAlice commented Jul 29, 2020

@ep1cman - i mentioned your above comment here: #103261 (comment)

@connor4312 connor4312 assigned connor4312 and unassigned weinand Jul 29, 2020
@JWess
Copy link

JWess commented Aug 4, 2020

I'm having the same issue with auto-attach not working on 1.47.3

@connor4312 connor4312 added this to the July 2020 milestone Aug 5, 2020
@connor4312 connor4312 added the bug Issue identified by VS Code Team member as probable bug label Aug 5, 2020
@connor4312
Copy link
Member

This will be fixed in the upcoming stable release next week, and also available in the next VS Code Insiders

@isidorn isidorn added the verified Verification succeeded label Aug 6, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Sep 20, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

7 participants