Vite+ Beta

#1

Post by ErenayDev » Thu, Jul 02, 2026, 11:30 AM UTC

Vite+ Beta
voidzero.dev

Re: Vite+ Beta

#2

Post by ivanjermakov » Thu, Jul 02, 2026, 12:01 PM UTC

Can it be used for Node builds or browser-only same as Vite?

Re: Vite+ Beta

#3

Post by curtisblaine » Thu, Jul 02, 2026, 12:09 PM UTC

ivanjermakov wrote: post #2

Can it be used for Node builds or browser-only same as Vite?

I'm always curious of the use case when someone proposes Node code bundling. What's the advantage? Obfuscation in SEA?

Re: Vite+ Beta

#4

Post by tvbusy » Thu, Jul 02, 2026, 12:10 PM UTC

ivanjermakov wrote: post #2

Can it be used for Node builds or browser-only same as Vite?

It uses Vite so the same limitations as Vite. However, I have been using Vite for my NestJS servers without any problem with `vite-plugin-node`. See example at https://github.com/leosuncin/nest-vite-example/blob/master/v...

Re: Vite+ Beta

#5

Post by ivanjermakov » Thu, Jul 02, 2026, 12:14 PM UTC

curtisblaine wrote: post #3

ivanjermakov wrote: post #2

Can it be used for Node builds or browser-only same as Vite?

I'm always curious of the use case when someone proposes Node code bundling. What's the advantage? Obfuscation in SEA?

Running typescript without compilation is still tricky with plain Node. `vite dev` has amazing DX not available for Node programs. I'm wondering if Vite+ tackles this problem.

Re: Vite+ Beta

#6

Post by curtisblaine » Thu, Jul 02, 2026, 12:20 PM UTC

ivanjermakov wrote: post #5

curtisblaine wrote: post #3

Earlier quoted context omitted.

I'm always curious of the use case when someone proposes Node code bundling. What's the advantage? Obfuscation in SEA?

Running typescript without compilation is still tricky with plain Node. `vite dev` has amazing DX not available for Node programs. I'm wondering if Vite+ tackles this problem.

Don't we have `tsx` and `nodemon` (or the native Node reloader) for that? What are the DX gaps you see on the server side out of on-the-fly transpilation and reload on watch?

Re: Vite+ Beta

#7

Post by colesantiago » Thu, Jul 02, 2026, 12:20 PM UTC

Is there a subscription with this?

I'm just wary about anything with a '+' and I assume there is a subscription attached to it.

Looking at this it doesn't look like it.

Re: Vite+ Beta

#8

Post by khurs » Thu, Jul 02, 2026, 12:22 PM UTC

colesantiago wrote: post #7

Is there a subscription with this? I'm just wary about anything with a '+' and I assume there is a subscription attached to it. Looking at this it doesn't look like it.

Says:

"It is fully open source under the MIT license"

Re: Vite+ Beta

#9

Post by incrudible » Thu, Jul 02, 2026, 12:22 PM UTC

I have removed vite because dev build and reload is noticable slower than just esbuild and browser refresh. Vite does nothing for me that an LLM can not just trivially rebuild in a bespoke manner.

YMMV

Re: Vite+ Beta

#10

Post by afavour » Thu, Jul 02, 2026, 12:22 PM UTC

curtisblaine wrote: post #3

ivanjermakov wrote: post #2

Can it be used for Node builds or browser-only same as Vite?

I'm always curious of the use case when someone proposes Node code bundling. What's the advantage? Obfuscation in SEA?

In my experience the bundling isn’t really the important aspect (though it also doesn’t harm anything), it’s more just having an ecosystem of plugins for code transpiling, static asset inclusion (e.g. text files) etc and a configuration format folks are already used to.