Live data from Hacker News

Vite+ – Unified toolchain for the web

viteplus.dev

101–110 of 151 posts

Re: Vite+ – Unified toolchain for the web

#101
post #78

Earlier quoted context omitted.

I was on the conference where it was announced. They plan to finish rewriting all the eslint/tsc/prettier/bundler/nx/minifier stuff in rust and give it single config instead of all of those tools having its own ast parser, alias rules and 5 incompatible babel versions. If anything, FE tooling starts looking like it moves to more sane place. Also Anthony Fu is cool

Yes but is it worth paying a monthly subscription in order to avoid some config files? I donno. Then you will have the problem in if things go wrong or if you do something very different it's closed source so it won't be easily fixed or prioritized since there is no community.

I dunno really. I'm pretty sure my organization will be willing to cough up the fee.

Me personally -- I would rather see it staying fully opensource and be funded through open collective or EU grants or something, like a lot of core stuff should. The fact this model doesn't work is sad.

I feel that something that the whole FE community gravitates to converge on should stay that way to prevent rag pulls and license dramas, otherwise it sabotages the process of converging on the same set of tools in the first place. Then the whole work will be wasted and eventually the project will die out and we get back to the same mess.

That being said, I get that the problem they are aiming to solve is a big pain point and whoever solves it -- they deserve money, but don't deserve to keep the whole community hostage to their whims indefinitely.

Then again, if people can pay 20 bucks a month for oracle lottery tickets selling infinite wisdom one token at time, why not pay actually helpful people doing great tools.

Re: Vite+ – Unified toolchain for the web

#102
post #73

Earlier quoted context omitted.

No it's not out of date. It's very much the reality. Every new tool is just one more thing added on top. When I have to do something in a JS/TS repo at work it's always a surprise which epoch of JS hype stuff I find. Today I fix ESLint warnings, tomorrow it's Biome errors, then I need to figure out how to override dependencies in pnpm, but oh no there's a some bug in Bun now. Did I forget the 10249120491412e12 config…

If your complaint is that there are too many problems in too many different tools , then you sound like the perfect target for a UNIFIED tool that abstracts over others. Because of Vite, there was a total of ZERO work from my side involved in changing from Rollup to Rolldown, or from babel to Esbuild to SWC. The Rust/Go/uv model is the one to go. This is ONE step in this direction.

Lets assume Vite+ ends up working super well. Then projects using it could very well end up being a delight to work with. But that's a big IF. They'd have to resist the urge to integrate with the many other parts of JS and basically say no to a lot of requests.

But many projects won't adopt it. There are so many competitors all with their own little ecosystems. So in the end, I'll still have to fix all the issues I fix right now PLUS the issues that Vite+ will add on its own.

The only chance I see for something like this actually working is if something like Node/NPM decided to add a default formatter, linter, and so on.

Re: Vite+ – Unified toolchain for the web

#103
post #12

I don't get it. If I'm looking for a new webdev stack, I would obviously want something free, open source. A big "Request early access" followed by a contact form at the top of the landing page is an instant redflag of vendor locking, who would ever want that?

It's also explicitly not FOSS, "Vite+ will be source-available" it says on the page so effectively proprietary for all intents and purposes. A free pricing plan will be in place that will initially be very generous, but as time goes on and the business will need more money, it'll slowly get worse and worse. Eventually you'll need to migrate away or cough up serious money. So yeah, not sure who'd go for this.

Oh I'm pretty sure my org will be happy to cough up the money the same way it pays for all kinds of other things supporting development. If anything, it could even save money on compute and net while doing it too.

I'm concerned that it erodes trust into vite and makes all the other open source maintainers contributing to /the commons/ asking some questions.

There is nothing really special about vite too. It's important, sure, but there is a lot of important open source projects that also need funding. Can all of them pull the same trick?

Re: Vite+ – Unified toolchain for the web

#104
post #83
post #79

Earlier quoted context omitted.

Same here, since 2001. It pains me that so many SaaS go for Next.js based SDKs, but at least it is the closest to Spring/Quarkus/ASP.NET in spirit.

If I had my way I would still be writing ASP.NET WebForms, but the market decided to move. I don't even know if it still works. Hot take but: it took 20 years for Next.js to catch up to 10% of WebForms offered. But if people want whatever Next.js offers to build their copycat SaaS with shadcn/ui, so who am I to argue.

Kind of frustrating to watch indeed. Have similar complaints for GUI apps on the desktop, really feels we went backwards from building great GUIs in 10 minutes using WYSIWYG to never really seeing the GUI until it compiles a bunch of XML and you somehow hope it will match what is needed.

Productivity is now wasted trying to make sure that buttons work when pressed or scratching the heads why box is not aligned with another programatically.

Re: Vite+ – Unified toolchain for the web

#105
post #84

Earlier quoted context omitted.

No it's not out of date. It's very much the reality. Every new tool is just one more thing added on top. When I have to do something in a JS/TS repo at work it's always a surprise which epoch of JS hype stuff I find. Today I fix ESLint warnings, tomorrow it's Biome errors, then I need to figure out how to override dependencies in pnpm, but oh no there's a some bug in Bun now. Did I forget the 10249120491412e12 config…

Greybeard (35) here. When these cynical takes were crafted, Angular, AngularJS, Aurelia, Backbone, Ember, Knockout, React and Vue were all competing for mindshare, with new members joining/leaving that group every month (anyone remember OJ.js and Google FOAM?) being compiled by traceur, 6to5, the Google Closure Compiler and others from (Iced) CoffeeScript, TypeScript, ES6, Atscript, Livescript and Closurescript. We h…

Okay fair point, the various *Scripts predates my entry into the developer workforce somewhat.

But just in the repos at work I deal with: yarn, npm, pnpm, bun, NextJS, biome, Prettier, ESlint, Vite, Vitest, Jest, Turbopack and esbuild. At least those are the things I remember right now. They all have their idiosyncracies and issues. They all require learning slightly different configs. Nothing is compatible with anything else. I can't take one library and `npm link` it into another because their toolchains are completely different. Then you have the whole topic of exporting TS vs. JS, different module types, module resolution, custom module resolution rules to accomodate for how some outdated plugin somewhere works.

And this really is just the tip of the iceberg.

I wish these folks the best and I hope I'm wrong and in a few years all of this is replaced by `vite lint` and `vite build`. But my past experience tells me that I'll simple add one more word to this list.

Re: Vite+ – Unified toolchain for the web

#106
post #84

Earlier quoted context omitted.

No it's not out of date. It's very much the reality. Every new tool is just one more thing added on top. When I have to do something in a JS/TS repo at work it's always a surprise which epoch of JS hype stuff I find. Today I fix ESLint warnings, tomorrow it's Biome errors, then I need to figure out how to override dependencies in pnpm, but oh no there's a some bug in Bun now. Did I forget the 10249120491412e12 config…

Greybeard (35) here. When these cynical takes were crafted, Angular, AngularJS, Aurelia, Backbone, Ember, Knockout, React and Vue were all competing for mindshare, with new members joining/leaving that group every month (anyone remember OJ.js and Google FOAM?) being compiled by traceur, 6to5, the Google Closure Compiler and others from (Iced) CoffeeScript, TypeScript, ES6, Atscript, Livescript and Closurescript. We h…

Slightly older here although I don't see how that matters.

No, it doesn't mean people in 2025 can't complain. Hype based noise that gets in the way of people doing good work should be decried even if someone else somewhere (or somewhen) has it bad too.

This isn't a competition of badness.

Gates open. Come on in!

Re: Vite+ – Unified toolchain for the web

#107
post #74

Earlier quoted context omitted.

Eslint did a massive breaking change with it's config format not too long ago, and still doesn't seem like it knows what it wants to be when it grows up (I was happily using eslint for things prettier does...)

Fine, updating 8 to 9 sucked for you, and I believe you. I did mention that ESLint is the "problematic" one, that people are working hard to replace. If so what's the problem? What about the other tools?

"Ok you directly addressed one of my hand picked examples, clearly showing your point and why my example wasn't a good one. Now address all my other ones before I consider your perspective might be valid!"

This is like the comment version of the gish gallop.

Re: Vite+ – Unified toolchain for the web

#108
post #52
post #12

I don't get it. If I'm looking for a new webdev stack, I would obviously want something free, open source. A big "Request early access" followed by a contact form at the top of the landing page is an instant redflag of vendor locking, who would ever want that?

Keep in mind that this is a super early preview. It will be source-available when stable. And it will be free for the community , while companies will have to pay.

Source available is not open source. It does not alleviate the concerns raised by OP or it's top child reply

Are you affiliated with this project? Based on your comment history, you seem to be

Re: Vite+ – Unified toolchain for the web

#109
post #99
post #85

Earlier quoted context omitted.

TIming was hardly an issue since they didn't produce anything important. moreover, their first focus was on formatter, which can be as low priority for any dev as it gets. Even Vite+ is focused on vite and rolldown first, and formatter last.

Sure, but a large part of why they never managed to produce anything useful is because SWC/ESBuild basically made the whole Rome architecture obsolete and killed all momentum around the project before they got anywhere.

what has SWC has to do with thier success or failure for Rome? Rome was VC funded, afaik, turbopack still persists despite it being effectively obsolete with vite

Re: Vite+ – Unified toolchain for the web

#110
post #8

Earlier quoted context omitted.

This cynicism is several years out of date. The current dominant toolchain has been very stable for years now, and is much better than the mess of Webpack/Rollup/Brunch/Grunt/Gulp/Bower/Browserify/Parcel/Snowpack/Turbopack/Babel/etc/etc. The only problem is that NOW there are too many separate different tools that aren't bundlers, so in addition to Vite one also has to configure Prettier, Eslint, Vitest, Typescript,…

> very stable for years now Especially eslint with their decision to change configuration format in a way that breaks all and every plugin, tutorial, project in existence as a giant "fuck you" to the whole ecosystem and all web developers of the world.

Still on v8 and won't upgrade. I would rather switch to Biome. It's annoying investing more time into tooling than actual work.
Post reply on HN