Keep using vite instead of vike cli

[zhujiageng]

Vite is a widely supported tool, and using vite cli ensures maximum compatibility and extensibility. If you switch to vike cli, then the runners that originally used @nx/vite in the nx monorepo will no longer work.

[brillout]

I agree in principle, and we very much try to avoid breaking Vite's API as much as possible. That said, Vike's CLI unlocks many new capabilities that are already being leveraged by vike-server and vike-react-rsc.

AFAICT (but correct me if I'm wrong) deprecating Vite's CLI is just a negligible DX degradation. That's why, all-in-all, we decided to go down the path of deprecating Vite's CLI.

As for Nx, I guess there is a workaround? There are many Vite-based frameworks that also don't support Vite's CLI — how do they integrate with Nx?

It would be nice to add some documentation about using Vike + Nx at vike.dev/nx. Contribution welcome.

[zhujiageng]

There is a workaround, but the cost is that the hit rate of nx's cache will significantly decrease.

[brillout]

How so?

[zhujiageng]

use "nx:run-commands" executor instead of "@nx/vite"

[AgentEnder]

This doesn't impact the cache rate, @nx/vite infers run-commands based targets as well you can simply remap the command :)

I'm a maintainer on Nx and also use vike frequently.

[brillout]

@zhujiageng Vike recently added first class support for third-party CLIs, see note at https://vike.dev/cli.