jsconfig.json path alias alternatives are not working

[Nefcanto]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #43-Ubuntu SMP Wed Jun 15 12:54:21 UTC 2022
Binaries:
  Node: 16.17.1
  npm: 8.19.2
  Yarn: 1.22.19
  pnpm: N/A
Relevant packages:
  next: 12.3.2-canary.20
  eslint-config-next: 12.3.1
  react: 18.2.0
  react-dom: 18.2.0

What browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

Describe the Bug

Use multiple paths for alias in jsconfig.json. It does not resolve the alternative paths.

Expected Behavior

It should consider all paths that are provided for any alias in jsconfig.json paths.

Link to reproduction

https://stackblitz.com/edit/nextjs-34trut?file=pages%2Findex.js

To Reproduce

1- Create a next app
2- Create two components
3- Create alias for them in jsconfig.json
4- Create one third alias, to include them both
5- Import using those aliases, the alias that contains both of them fails

[vercel-release-bot]

This issue has been automatically marked as stale due to two years of inactivity. It will be closed in 7 days unless there’s further input. If you believe this issue is still relevant, please leave a comment or provide updated details. Thank you.