You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ccarcaci opened this issue
Dec 14, 2021
· 4 comments
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Does this issue occur when all extensions are disabled?: Yes
When using the "double-dot parent folder indirection" in launch configuration (see image) the debugger stops working properly with typescript and source maps.
OS Version:
Ubuntu Linux Linux ccarcaci-N56JN 5.11.0-41-generic #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
I have the same problem also on OSX on a different machine.
Select menu entry File > Open workspace from file...
Select the workspace.code-workspace from parent-cwd-issue/multi-folder/workspace-launch.
Run npm build pointing your console to parent-cwd-issue/multi-folder/service-code.
Set a breakpoint in the index.ts file.
Open Run&Debug tab.
Launch "multi folder" runnable configuration.
Debugger is not stopping correctly at the breakpoint.
Open the file parent-cwd-issue/multi-folder/service-code/build/src/index.js.
Set a breakpoint.
Open Run&Debug tab.
Launch "multi folder" runnable configuration.
Debugger works correctly on compiled code (see image).
What's the difference?
The single-folder package has a launch configuration which uses the cwd default value (I've tried using a path without parent indirection and it works either).
The multi-folder package has a launch configuration which specifies a parent indirection in the cwd setting.
The text was updated successfully, but these errors were encountered:
By default, VS Code will only scan the workspace folder for sourcemaps, and this adjusts that. We actually have logic to do this automatically, but it was only activated if a program was set, which is not the case for you.
You also most likely want to remove the disableOptimisticBPs.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
bugIssue identified by VS Code Team member as probable bugdebugDebug viewlet, configurations, breakpoints, adapter issuesverifiedVerification succeeded
Does this issue occur when all extensions are disabled?: Yes
When using the "double-dot parent folder indirection" in launch configuration (see image) the debugger stops working properly with typescript and source maps.
Ubuntu Linux
Linux ccarcaci-N56JN 5.11.0-41-generic #45~20.04.1-Ubuntu SMP Wed Nov 10 10:20:10 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
I have the same problem also on OSX on a different machine.
Steps to Reproduce.
Working case:
parent-cwd-issue/single-folder
.npm build
pointing your console toparent-cwd-issue/single-folder
.Broken case:
parent-cwd-issue/multi-folder/workspace-launch
.npm build
pointing your console toparent-cwd-issue/multi-folder/service-code
.parent-cwd-issue/multi-folder/service-code/build/src/index.js
.What's the difference?
The single-folder package has a launch configuration which uses the
cwd
default value (I've tried using a path without parent indirection and it works either).The multi-folder package has a launch configuration which specifies a parent indirection in the
cwd
setting.The text was updated successfully, but these errors were encountered: