I'm currently trying to find out about this as well.

Posted a new question before finding this:
#4860

Did you ever find a solution?

I'm looking for this as well.

I am still looking too...

I am using the recommended NextJS configuration for the vscode debugger and I am having issues with breakpoints working within my packages. Is this related?

Same problem here as well, since migration to turborepo debugging not working anymore...

This is a pretty common thing to do in other ecosystems and on larger projects. Sometimes its a monorepo, other times 80 microservice repos on a minikube - the principle is the same - only run what you must in debug mode, run everything else as you normally would.

• Start the turbo dev or turbo start tasks as you normally would.
• Don't start them all, filter out the services you wish to debug turbo dev -F '!@acme/web'. Note: the ' are important to prevent Bash from interpreting the ! character as a history expansion event and allow Turbo to correctly process the negative filter.
• Now, run the VSCode debug configuration only for the services you actually wish to debug:

// .vscode/launch.json
    {
      "name": "Next.js: debug full stack",
      "type": "node-terminal",
      "request": "launch",
      "command": "npm run dev",
      "cwd": "${workspaceFolder}/apps/web",
      "serverReadyAction": {
        "pattern": "started server on .+, url: (https?://.+)",
        "uriFormat": "%s",
        "action": "debugWithChrome"
      }
    }

If you need to run more than 1 debugger, VSCode is capable to run tasks in parallel, although it will get confusing soon. The important part of the launch config above is "cwd": "${workspaceFolder}/apps/web" which sets the work directory. You might think that running npm run -w apps/web dev should technically work similarly to changing the cwd, but in practice, setting the cwd explicitly ensures that all path resolutions and VSCode's environment variables when attaching to the debug session are correctly aligned with the workspace directory. 🤷‍♂️

Bonus points:

Since Next.JS is a true full-stack framework, we shouldn't forget CLI script debugging. Turborepo excells at having us decouple administrative scripts from our applications, which we usually place either in /packages/scripts/ or into /tooling/scripts/. The principle is the same, and you don't need turbo for it.

• You run whatever supporting services you need to run via Turbo, as you normally would.
• This time no need to filter out anything, as CLI scripts don't have a dev and wouldn't run anyway.
• Run the following VSCode launch config:

// .vscode/launch.json
    {
      "type": "node-terminal",
      "request": "launch",
      "name": "Debug CLI Script",
      "command": "npm run cli src/example.ts",
      "cwd": "${workspaceFolder}/tooling/scripts",
      "skipFiles": ["<node_internals>/**"]
    }

This is my working launch.json file with NestJs ,NextJs setup
file: .vscode/launch.json

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Debug API",
      "type": "node",
      "request": "launch",
      "runtimeExecutable": "pnpm",
      "runtimeArgs": ["run", "start:debug"],
      "cwd": "${workspaceFolder}/apps/api"
    },
    {
      "name": "Debug Web",
      "type": "node-terminal",
      "request": "launch",
      "command": "pnpm run dev",
      "cwd": "${workspaceFolder}/apps/web"
    }
  ],
  "compounds": [
    {
      "name": "Debug All",
      "configurations": ["Debug API", "Debug Web"]
    }
  ]
}