fix(vite): get tsconfig from new path including target

[ms-tng]

Current Behavior

Since v18.2.3 (e4c4697f69cf29c50aced1997715a7da5f680e23) the tsconfig.generated.json file generated if "buildLibsFromSource": false is placed under a path containing the current build target. The nx-tsconfig-paths plugin of @nx/vite was not updated accordingly, so now it doesn't find tsconfig.generated.json, effectively causing @nx/vite to ignore the "buildLibsFromSource": false setting.

Expected Behavior

With this PR, nx-tsconfig-paths finds tsconfig.generated.json at the correct path, so "buildLibsFromSource": false works as it did before v18.2.3.

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	May 7, 2024 11:58am

[nx-cloud[bot]]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 88fe30bdd206aa3e541c4eaa699492d53532f2e2. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --targets=e2e,e2e-ci --base=0e56533d014ec324e4706ac943c0daa834b44719 --head=88fe30bdd206aa3e541c4eaa699492d53532f2e2 --parallel=1
• nx affected --targets=lint,test,build --base=0e56533d014ec324e4706ac943c0daa834b44719 --head=88fe30bdd206aa3e541c4eaa699492d53532f2e2 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=0e56533d014ec324e4706ac943c0daa834b44719 --head=88fe30bdd206aa3e541c4eaa699492d53532f2e2
• nx documentation --no-dte
• nx affected -t e2e-macos-ci --parallel=1 --base=0e56533d014ec324e4706ac943c0daa834b44719 --head=88fe30bdd206aa3e541c4eaa699492d53532f2e2

---

Sent with 💌 from NxCloud.

[github-actions[bot]]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.