Monorepo self-referencing package imports don't resolve in certain cases with Turbopack

[timneutkens]

Link to the code that reproduces this issue

#66486

To Reproduce

⚠️ I've already opened a failing test here: #66486

For the original reproduction these are the steps:

1. Clone repository: https://github.com/juliusmarminge/turbo-self-referencing
2. Run commands:

pnpm install
cd internal-pkg
pnpm build
cd ../next-app
pnpm dev

3. Open http://localhost:3000
4. Observe the error

Current vs. Expected behavior

Expected: No build error
Current:

./internal-pkg/dist/index.js:1:1
Module not found: Can't resolve '@repo/internal-pkg/env'
> 1 | import { env } from '@repo/internal-pkg/env';
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  2 |
  3 | console.log({
  4 |     env

https://nextjs.org/docs/messages/module-not-found

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: <redacted>
  Available memory (MB): 49152
  Available CPU cores: 16
Binaries:
  Node: 18.20.2
  npm: 10.5.0
  Yarn: N/A
  pnpm: 8.15.7
Relevant Packages:
  next: 15.0.0-canary.7 // Latest available version is detected (15.0.0-canary.7).
  eslint-config-next: 15.0.0-canary.7
  react: 19.0.0-rc-f994737d14-20240522
  react-dom: 19.0.0-rc-f994737d14-20240522
  typescript: 5.3.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), next build (local)

Additional context

No response

[mischnic]

@vhpx Please open a new issue with a reproduction.

This specific case was fixed by vercel/turborepo#8820 / #68070

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.