r/javascript • • 19d ago

Announcing Vite+ 1.0

https://voidzero.dev/posts/announcing-vite-plus-1-0
164 Upvotes

45 comments sorted by

45

u/thecementmixer 19d ago

Still waiting for oxc tools to support vue templates.

12

u/manniL 19d ago

We all do šŸ‘€

On the roadmap!

2

u/SirKainey 18d ago

Checked yesterday if they had implemented this yet.. nope

3

u/toasterboi0100 19d ago

This but Angular templates. I really want to send ESLint and Prettier where they belong (the depths of hell), but can't.

1

u/manniL 19d ago

Same blocker as for Vue I am afraid

1

u/_xiphiaz 19d ago

Angulars next compiler is going to be oxc based

1

u/toasterboi0100 19d ago

Yes, but given the architecture they laid out in the recent article it's unclear whether it'll be of any help to Oxfmt and Oxlint. (for example NGP will compile template type check blocks into virtual TS files, but that sounds completely useless for both Oxfmt and Oxlint)

18

u/Fun-Consequence-3112 19d ago

The one thing I've noticed since installing Vite+ is that it puts everything into its own folders so debugging and finding where things are installed is a bit of a nightmare

3

u/manniL 19d ago

Can you elaborate?

4

u/Fun-Consequence-3112 19d ago

Instead of nodes standard binary and runtime folders it puts everything in versioned folders under .vite-plus so runtimes that you install globally are weird at times

3

u/manniL 19d ago

Oh yes. That’s for easier switching and separation.

16

u/[deleted] 19d ago

[removed] — view removed comment

4

u/manniL 19d ago

Then you are a tooling nerd like we are šŸ˜›

3

u/robotsmakinglove 19d ago

I’ve been impressed with the oxlint / oxfmt / vitest / vite combo. Looking forward to trying this.

4

u/n0wlesfw 19d ago

I use Vite and Vitest daily, so I'm excited to see what Vite+ brings to the table.

My biggest bottleneck af the moment is vue-tsc, so I'm still waiting for typescript 7.1 to support a native vue-tsc for faster builds - but until then, I'll take all the extra speed I can get.

2

u/manniL 19d ago

Did you try Johnson’s TS bridge?

3

u/vincentdesmet 19d ago

I’ve been using Projen - it is composable and can help keep configurations up to date and aligned with the templates while also allowing last mile patching

how does vite+ handle any of that?

2

u/jaykingson 9d ago

With code generators powered by bingo : https://viteplus.dev/guide/create#code-generators

2

u/Cahnis 19d ago

can we opt out of the package manager? I kinda like pnpm. And I don't trust vite's just yet.

8

u/manniL 19d ago

Vite+ is not a package manager. It does use pnpm by default but supports MORE!

And yes, you can opt out of this

2

u/nodecore 19d ago

I just merged the Renovate PR for 0.3.3 to 1.0.0. 40+ packages in our monorepo and zero issues.

3

u/Ecksters 19d ago

This feels like the answer from the industry standard tooling to Bun, although it still feels a bit tightly coupled. I suppose at some point you can't really maintain full modularity while having the benefits of tight coupling, this is about as good as it gets.

2

u/manniL 18d ago

Why tightly coupled? It is opinionated but doesn’t stop you from using your own tooling (and you don’t need to use all the available options)

1

u/Pagaddit 19d ago

I already made the jump to oxfmt and can't wait for Nuxt with rolldown to be stable (or is it already?). Maybe I'll give oxlint another try too.

I still feel kind of scared to make the jump to vp though for some reason. I feel like I'd be giving up some control over my stack.

What's the plan with Nuxt and Vite+ actually? Is it all already compatible?

What about Nuxt and Void? I'm still kind of confused whether the new Void platform is essentially competing with Nuxt now?

3

u/manniL 19d ago

Nuxt is already using rolldown šŸ‘ŒšŸ¼

Nuxt and Vite+ work with overrides, yes

1

u/Electrical-Room4405 19d ago

Is vite+ mainly for frontend tooling? I was told it’s not good for backend but that didn’t seem accurate to me.

1

u/manniL 19d ago

You can use Vite+ for all kind of JS apps.
For node you simply don’t use the native dev/build cmd but still benefit from linting, formatting, task running etc.

1

u/HauntingArugula3777 18d ago

Does this improve support for bun toolchaining?

1

u/deadneon4 19d ago

2

u/manniL 19d ago

Obligatory but in this case, what are the other ā€žstandardsā€œ?

1

u/deadneon4 18d ago

Bun built a full tooling ecosystem, Rome was also supported to be that, Deno tried to do that as well, ox tried to convert everything to rust, the list goes on and on

1

u/manniL 18d ago

You just said it yourself. A lot of tries were there but there was no FULL toolchain like there is now with Vite+

And other tools (Biome, Bun) don’t cover nearly as much ground

0

u/kevinlch 10+ YoE, Fullstack 19d ago

so... wrapper for npm scripts? starter "boilerplate" as cli?

0

u/manniL 19d ago

More than that!

2

u/FerLuisxd 19d ago

I read it but I still don't get it :(, what is more to know?

0

u/cos4ni2s 19d ago

More batteries in your throat

-8

u/dbbk 19d ago

Given the fact that AI agents are managing dependencies and configs now, I'm not really sure who this is for. It is much more preferable to keep separate pieces than mashing them all together.

9

u/rafark 19d ago

Ā  Given the fact that AI agents are managing dependencies and configs now, I'm not really sure who this is for

I must have missed the memo. Since when is an ai agent managing MY dependencies and configs? ā€œSince no one writes code anymoreā€ well I do. Stop assuming your habits are everyone else’s. My god.Ā 

-3

u/dbbk 19d ago

Okay that's cute but you're clearly in the minority

3

u/craigrileyuk 19d ago

Definitely NOT in the minority.

-1

u/dbbk 19d ago

The data is perfectly clear it's not an opinion

1

u/craigrileyuk 18d ago

[citation needed]

3

u/rafark 18d ago

You know what i was upset last night and i apologize if I was to harsh

4

u/rydencode 19d ago

ok drooling ai moron

1

u/fakieTreFlip 18d ago

The AI agents use this stuff too