Link to the code that reproduces this issue

https://github.com/Yonom/turborepo-bug-report

To Reproduce

next dev --turbo

Current vs. Expected behavior

Expected: next dev --turbo should not result in a build error, if next dev (without turbopack) compiles.

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.3.0: Thu Jan  2 20:24:16 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 22.14.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: 10.9.0
Relevant Packages:
  next: 15.3.1 // Latest available version is detected (15.3.1).
  eslint-config-next: 15.3.1
  react: 19.1.0
  react-dom: 19.1.0
  typescript: 5.8.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Turbopack

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

I use a shared tsconfig.base.json with path aliases like:

{
  "compilerOptions": {
    "paths": {
      "@/*": ["./*"],
      "package1": ["./packages/package1/src"],
      "package2": ["./packages/package2/src"]
    }
  }
}

Each project extends this base config and sets its own baseUrl:

{
  "extends": "../../tsconfig.base.json",
  "compilerOptions": {
    "baseUrl": "."
  }
}

This setup works with tsc, but Turbopack fails.