fix(vite): fall back to file matching when resolved file does not exist in nx-vite-ts-paths plugin

[estebanfelipep]

The fallback path resolution was only happening if the resolvedFile was a falsy value, so it was returning inexistent filepaths.

This pull request includes a small but important change to the packages/vite/plugins/nx-tsconfig-paths.plugin.ts file. The change improves the reliability of resolving file paths by checking if the resolved path exists before proceeding with fallback file matching.

• packages/vite/plugins/nx-tsconfig-paths.plugin.ts: Added a check to verify if the resolved file path exists before using fallback file matching.

Current Behavior

The resolver doesn't resolve the full file path, it ignores the file extension. For example, for a path like this:
import mergeClassNames from '@projects/global/utils/mergeClassNames'

It resolves to
absolutePath.../projects/libs/global/src/utils/mergeClassNames

When vite is building a project, it doesn't find the file and it errors.

This happens because the resolved file path is not a falsy value, thus, it doesn't run the fallback file path matching.

Expected Behavior

What is expected is that it resolves to (notice the file extension)
absolutePath.../projects/libs/global/src/utils/mergeClassNames.ts

Related Issue(s)

[vercel]

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

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Jan 29, 2025 10:31am

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 7e371d9.

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-c...	✅ Succeeded	30m 25s	View ↗
nx run-many -t check-imports check-commit check...	✅ Succeeded	14s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	2s	View ↗
nx-cloud record -- nx format:check --base=7d52f...	✅ Succeeded	23s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	21s	View ↗
nx documentation --no-dte	✅ Succeeded	49s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-01-29 11:02:22 UTC

[leosvelperez]

Thanks for the contribution!