Vite+ – Unified toolchain for the web
71–80 of 151 posts
Re: Vite+ – Unified toolchain for the web
#72I like Vite a lot, but (some feedback from the team) you need to give me more marketing up front to convince me why I would want more javascript. I already feel like I have too much. The comments here would echo the same.
I honestly don't understand the point you are making. What do you mean?
Re: Vite+ – Unified toolchain for the web
#73Earlier 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,…
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.
Re: Vite+ – Unified toolchain for the web
#74Earlier quoted context omitted.
What's not stable about Vite, ESLint, Typescript, Prettier? Apart from Vite itself, those have been standards for 8-10 years, and Vite itself has successfully replaced a huge mess of other tools. I agree that ESLint can become a mess, which is why I'm ok with a new competitor that doesn't require the extra configuration. Sure: they're also replacing Prettier (unnecessary) but everyone can keep using Prettier and chan…
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?
Re: Vite+ – Unified toolchain for the web
#75I like Vite a lot, but (some feedback from the team) you need to give me more marketing up front to convince me why I would want more javascript. I already feel like I have too much. The comments here would echo the same.
Its actually more rust and less js.
Re: Vite+ – Unified toolchain for the web
#76Earlier quoted context omitted.
What's not stable about Vite, ESLint, Typescript, Prettier? Apart from Vite itself, those have been standards for 8-10 years, and Vite itself has successfully replaced a huge mess of other tools. I agree that ESLint can become a mess, which is why I'm ok with a new competitor that doesn't require the extra configuration. Sure: they're also replacing Prettier (unnecessary) but everyone can keep using Prettier and chan…
If I stop working on a project for 3 years, will I still be able to compile it, without losing an unpredictablt amount of time to fixing the toolchain? If not, then its not really stable, is it?
With version pinning and lockfiles, sure.
Updating is a different matter, if you're using multiple tools, hundreds of packages and several configuration files.
Which is why a unified tool that doesn't require configuring 20 tools at once is a good idea IMO.
Re: Vite+ – Unified toolchain for the web
#77I 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?
This is not a webdev stack. It is build tools. you do not ship them to your users (like react/vue) but are you used by developers for local build and CI servers for prod build.
As for why? some people have very large codebase and prefers their developers to have better UX and are willing to pay for it. lower CI/CD server costs also directly translate to cost savings if you are Replit or stackblitz,
You may not like it, and that is ok. as individual developers are already benefitting from vite. and will get rolldown soon.
Re: Vite+ – Unified toolchain for the web
#78Interesting, I am a heavy user of vite today and the featureset is interesting but I don't really understand how it will differ from "normal" vite and why I would pay for it.
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
Re: Vite+ – Unified toolchain for the web
#79Don't get me wrong but at this point you might as well just use Java instead of javascript to build web pages. Vite is basically replicating what one would expect as normal behaviour from the JDK + IDE has been doing since years. Javascript was meant to be readable for an open web, nowadays it is compiled into a puddle of text. It is OK to reinvent the wheel, it just doesn't look much better than the old one.
Using Java/.NET with server side rendered HTML + webpack/react for dynamic components (which nearly are non-existent with modern CSS). Works great.
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.
Re: Vite+ – Unified toolchain for the web
#80I have a hard time understanding what Vite does, so Vite+...
Vite is a Javascript bundler that abstracts transpilation/typechecking/minification/hot-reloading/etc, so you don't need a 300-line hand-crafted configuration line that constantly breaks, like it was in the past with Webpack. There's still (some) configuration but much less.
Vite+ is a tool similar to Rust Cargo or Go's toolchain that handles building (via Vite), testing, linting and formatting.