Turborepo@2 is no longer playing well with vscode debug terminal #8388
Replies: 3 comments
-
|
I second this. Launching the debugger with the original config throws this now: So the updated launch.json config now launches the debugger but the breakpoints won't work. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Converting to an issue! |
Beta Was this translation helpful? Give feedback.
0 replies
This comment was marked as spam.
This comment was marked as spam.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Summary
I'm not sure about creating an issue about this, but
turborepo@2no longer play well with vscode debug terminal. Running a task inturborepo@1(includingturborepo@1.13) in a vscode debug terminal triggers vscode debug breakpoints, but this behavior no longer happens when tryingturborepo@2.We can still use more traditional ways to debug a node application (the inspector protocol works like a charm), but the vscode debug terminal is such an straightforward approach I think it would be great to support it in turborepo.
Is this behavior expected?
Consider this sample repo as an example. the task
foo:turbocannot be debugged using a javascript debug terminal unlessturbo@1is installed. Setting{ "ui": "stream" }in theturbo.jsonconfig file does not solve the issue.Additional information
I wonder if
turborepo@2spawns child task in a different wayturborepo@1does. Maybe microsoft/vscode-js-debug#1101 (comment) is relevant.Example
https://github.com/notaphplover/turborepo-trap-issue
Beta Was this translation helpful? Give feedback.
All reactions