feat(vite): add tsconfig paths resolution plugin

[barbados-clemens]

Current Behavior

vite-tsconfig-paths plugin isn't able to work with tmp tsconfigs to make incremental building work

Expected Behavior

nx supports incremental building with vite

Related Issue(s)

TODO:

• [x] validation across different vite setups with/without buildable libs
• [x] write e2e tests
• [x] handle TODOs
• [x] cleanup register work within executor to just generate tsconfigs

Fixes #

[vercel[bot]]

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

Name	Status	Preview	Comments	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jul 17, 2023 3:22pm

[nx-cloud[bot]]

☁️ Nx Cloud Report

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

📂 See all runs for this branch

---

✅ Successfully ran 1 target

• nx affected -t e2e-macos --parallel=1 --base=187842e14c2d8b65d6c2b265502e2b08519acb7c --head=ce7876d052067c85630c75bf17ccc65b39bf330d

---

Sent with 💌 from NxCloud.

[mandarini]

Cool! So, yes, I tested on this repo: https://github.com/mandarini/vite-paths/tree/test-caleb on the branch test-caleb, which I added lots of interdependencies, and some to cover Storybook path resolution as well. All works great! So it's a ✅ from me, but with the question whether we really want to drop vite-tsconfig-paths completely, and not rely on it at all!

[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.