Linking incorrect package with optimizePackageImports when multiple versions are available in monorepo

[JAD3N]

Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/goofy-paper-l7f8zx

To Reproduce

1. Open reproducible link.
2. Run the dev task or pnpm install && cd packages/example-b && pnpm dev.
3. The example-b should not work as @chakra-ui/react@3 does not export Modal showing that it is linking to the incorrect package version.
4. Example A should work as expected and log the Modal function.

Current vs. Expected behavior

The expected behavior would be that each workspace package would link to it's dependencies (Chakra UI v2 for example-a and Chakra-UI v3 for example-b) when using optimizePackageImports. So example-a should link to V2 of Chakra UI and example-b should link to V3.

What seems to happen is that example-b will link to @chakra-ui/react@v2 only when @chakra-ui/react is included in the optimizePackageImports experimental setting, when it's not included everything works fine but just slower.

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.2.0-canary.26 // Latest available version is detected (15.2.0-canary.26).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A

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

Not sure

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

next dev (local)

Additional context

This problem only applies when using webpack and not turbo.