fix(vite): support incremental building when running 'serve'

[barbados-clemens]

closed #18458

Current Behavior

when using incremental building with vite buildLibsFromSource: false, vite would still reference the source code when running 'serve'.

Expected Behavior

incremental building works with serve as well as build.

Note: serve will need to depend on '^build' in order for it to work without manually building first.

Related Issue(s)

Fixes #18458

[vercel]

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	Aug 23, 2023 6:44pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 4e25cda. 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 8 targets

• linux nx affected --target=e2e --base=bbae14b9a7169fb7bad753aa20b4e7b39dac27a9 --head=4e25cda054d4bfdc7ef55ff578e9088bb12e1264 --parallel=1
• linux nx affected --target=test --base=bbae14b9a7169fb7bad753aa20b4e7b39dac27a9 --head=4e25cda054d4bfdc7ef55ff578e9088bb12e1264 --parallel=1
• linux nx affected --target=build --base=bbae14b9a7169fb7bad753aa20b4e7b39dac27a9 --head=4e25cda054d4bfdc7ef55ff578e9088bb12e1264 --parallel=3
• linux nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• linux nx affected --target=lint --base=bbae14b9a7169fb7bad753aa20b4e7b39dac27a9 --head=4e25cda054d4bfdc7ef55ff578e9088bb12e1264 --parallel=3
• nx-cloud record -- nx format:check --base=bbae14b9a7169fb7bad753aa20b4e7b39dac27a9 --head=4e25cda054d4bfdc7ef55ff578e9088bb12e1264
• linux nx documentation --no-dte
• macos nx affected -t e2e-macos --parallel=1 --base=bbae14b9a7169fb7bad753aa20b4e7b39dac27a9 --head=4e25cda054d4bfdc7ef55ff578e9088bb12e1264

---

Sent with 💌 from NxCloud.

[github-actions]

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.