Running `vp dev` on a new Astro project doesn't work

[joknoll]

Describe the bug

After creating an astro project with vp create astro the cli recommends to run

Next: cd astro-project && vp dev

But running vp dev starts the development server at 5173, which is not what astro does.

Running vp run dev works correctly.

It might be better to rather recommend running vp run dev instead of vp dev for astro projects.

This might be related to #912

Reproduction

https://stackblitz.com/~/github.com/joknoll/viteplus-astro

Steps to reproduce

No response

System Info

VITE+ - The Unified Toolchain for the Web

vp v0.1.13

Local vite-plus:
  vite-plus  v0.1.13

Tools:
  vite             v8.0.1
  rolldown         v1.0.0-rc.10
  vitest           v4.1.0
  oxfmt            v0.41.0
  oxlint           v1.56.0
  oxlint-tsgolint  v0.17.1
  tsdown           v0.21.4

Environment:
  Package manager  pnpm v10.32.1
  Node.js          v24.14.0 (engines.node)

Used Package Manager

pnpm

Logs

Validations

• Read the Contributing Guidelines.
• Check that there isn't already an issue for the same bug.
• Confirm this is a Vite+ issue and not an upstream issue (Vite, Vitest, tsdown, Rolldown, or Oxc).
• The provided reproduction is a minimal reproducible example.

[jong-kyung]

@fengmk2 Hi! I would like to work on this issue. Could you assign it to me?

[tobiasdiez]

@jong-kyung @fengmk2 What's the point of vp dev and vp build then in Astro or Nuxt projects? For me in a fresh nuxt project, they are not working at all (opening an empty dev server and failing during the build due to missing index.html).

Would it not be better to forward those commands to the corresponding nuxt/astro dev + build cmds?

Otherwise https://viteplus.dev/guide/dev should reflect that it's useless in metaframeworks.