You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Back in the vite-plugin-ssr days, it made sense for the user to directly use the $ vite CLI. But this has limitations: Vike should introduce its own CLI.
IMO: If we were to do that, I thought it would be easier to use vike to depend on vite and install only vike, instead of having people install vite and vike separately.
If this seems different from Vike's design policy, please forget it.
Description
Back in the
vite-plugin-ssr
days, it made sense for the user to directly use the$ vite
CLI. But this has limitations: Vike should introduce its own CLI.We'll most likely need a Vike CLI for #562, thus labeling as https://github.com/vikejs/vike/labels/server%20%F0%9F%8C%90. Also labelling as https://github.com/vikejs/vike/labels/high-prio%20%F0%9F%94%A5 because it's a blocker.
The text was updated successfully, but these errors were encountered: