Feature Request: Native Node.js Script Execution via `vp node` or `vp run`

[runyasak]

Description

Hi!

Right now, if I want to run a plain Node.js file with Vite+, I still have to use node directly or use vp env exec node test.js, which feels a bit outside the vp world. I think it would be really nice if Vite+ could run .js and .ts files natively, so we can stay in the vp ecosystem the whole time.

Suggested solution

Add a vp node command that runs a JavaScript or TypeScript file directly using Vite+'s managed runtime:

vp node index.js
vp node scripts/seed.ts

It would be great if this also:

• Supports TypeScript out of the box
• Respects path aliases from vite.config.ts
• Uses Vite+'s managed Node.js version

Alternative

If a new vp node command is too much, maybe vp run could also accept a file path directly:

vp run index.js

Or, the current vp env exec node test.js workaround could be shortened to something simpler.

Additional context

Vite+ already does a great job combining Vite, Vitest, Oxlint, Oxfmt, and more into one tool. Being able to run Node.js files directly would make it a complete toolchain for any JavaScript project, not just frontend. This would be a great DX improvement!

This is my first issue on this project — sorry if this has already been discussed before!
If you have any feedback or comments, do not hesitate to let me know.

Validations

• Read the Contributing Guidelines.
• Confirm this request is for Vite+ itself and not for Vite, Vitest, tsdown, Rolldown, or Oxc.
• Check that there isn't already an issue requesting the same feature.

[cpojer]

I think we should have this, but I don't know yet what the ideal setup is. Conceptually vp run <file> is very slick and minimal overhead.

[runyasak]

@cpojer Perhaps we could even go with just vp <file>?
It feels very natural, just like node <file>. 😊

[fengmk2]

Since vp already manages Node.js, wouldn’t running node directly be easier to understand? vp itself isn’t a JS runtime, so vp <file> would be confusing.

[cpojer]

@runyasak vp <file> is not great. We weren't planning on adding shorthands to the CLI.
@fengmk2 The use case is when the user isn't use Vite+ to manage their global node. Then they have to define a script/task to run a script with node. Another idea could be "implicit tasks", such as vp run 'node index.js', but I feel like that's not a good solution.

[fengmk2]

how about vpx index.ts?

But in that case, wouldn’t Vite+ effectively become a JS runtime? 😢

[rubenferreira97]

But in that case, wouldn’t Vite+ effectively become a JS runtime? 😢

I would like to think this as a JS runtime manager rather than a runtime itself.

Think of it like vp pm. It provides a unified interface, but there is still an underlying package manager doing the work. Similarly, vp run would just be a management layer over the underlying Node.js binary.

(I’ll be honest: I was really hyped for Vite+, but without this "glue," it hasn't quite clicked for me yet. For example, trying to run scripts like those mentioned in #1117 still feels fragmented because I have to step 'outside' the ecosystem to execute a simple file. If vp manages the environment, it feels only natural that it should be the entry point for execution.)

[runyasak]

Since vp already manages Node.js, wouldn’t running node directly be easier to understand? vp itself isn’t a JS runtime, so vp <file> would be confusing.

@fengmk2 Oh, I just realized that vp <file> could be confusing. I think vp run <file> is the better choice.

how about vpx index.ts?

Though I also love the idea of vpx as a shorthand alias — that would feel really nice to type.

To be honest, I didn't expect Vite+ to become a new JS runtime or anything like that.
I just thought it would be nice if there was a simple way to run a file as part of the workflow — nothing too deep. I noticed vp env already manages the Node.js version, so I wondered if running a file directly could naturally fit in there too, similar to how node <file> works.

That's just my personal expectation. Apologies if it doesn't align with the contributors' vision or the tool's purpose.