Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vite+ – Unified toolchain for the web

viteplus.dev

Post reply on HN
Print view View original

41–50 of 151 posts

Re: Vite+ – Unified toolchain for the web

#41

Post by c-hendricks »

avhception wrote: post #30
whstl wrote: 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,…

I'm not even a JS dev, I support the CI pipelines and Docker images and whatnot. It's something else every week. When I get it to work eventually, it's brittle as hell. I just want the madness to stop. I don't even care any more.

Anecdotal, but I switched our webpack configs with vote a few years ago and haven't had to touch it since.

Didn't have to touch the webpack stuff either. Perhaps the issues you're having are due to something else?

Re: Vite+ – Unified toolchain for the web

#43

Post by candiddevmike »

whstl wrote: post #20
skydhash wrote: post #15

Earlier quoted context omitted.

At this point, I don't want unified tools. I want stable ones. I'm fine with using a separate linter/formatter/transpiler/bundler/..., but why can't they just stay stable for a bit. The only two tools I like in the JS world is `yarn` and `prettier`. They're focused and do what they do well. But you add eslint and any of the others and their configuration is a full fledged turing machine. Even autotools feels nice in…

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...)

Re: Vite+ – Unified toolchain for the web

#45

Post by cowsandmilk »

boplicity wrote: post #39
whstl wrote: post #20

Earlier 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?

As someone who “owns” a framework at work that has been unfunded for several years, the answer is definitively yes. I haven’t touched the build toolchain in all those years and the project continues to build a dozen different JavaScript libraries with no issues across multiple Node.js upgrades.

The current version of webpack was released 5 years ago. You can keep using eslint 8 which was released 4 years ago. This really isn’t the constantly changing space it was in the 2010’s

Re: Vite+ – Unified toolchain for the web

#46

Post by hv42 »

I am wondering what vite+ will have that will really make it worth it compared to the "rstack" (i.e. rspack, rsbuild, rstest, rslint, etc.) rsbuild is already excellent and things like remote cache are on their roadmap?

Re: Vite+ – Unified toolchain for the web

#48

Post by thiht »

hv42 wrote: post #46

I am wondering what vite+ will have that will really make it worth it compared to the "rstack" (i.e. rspack, rsbuild, rstest, rslint, etc.) rsbuild is already excellent and things like remote cache are on their roadmap?

Familiarity I guess? I've never heard of rsbuild before. In comparison, the "Vite" name directly brings me joy and makes me think of high quality, enjoyable tooling.

Re: Vite+ – Unified toolchain for the web

#49

Post by skydhash »

whstl wrote: post #20
skydhash wrote: post #15

Earlier quoted context omitted.

At this point, I don't want unified tools. I want stable ones. I'm fine with using a separate linter/formatter/transpiler/bundler/..., but why can't they just stay stable for a bit. The only two tools I like in the JS world is `yarn` and `prettier`. They're focused and do what they do well. But you add eslint and any of the others and their configuration is a full fledged turing machine. Even autotools feels nice in…

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…

In my opinion, because there’s no core principles behind anything. jQuery was nice because it presented a nice API on to of the DOM. There was just this single layer that both your code and the libraries rely on.

But now there’s no unifying principles behind anything. No conventions. It’s just incantations to get thing working nicely together. It’s all preprocessing and post processing, code generation an what not.

Post reply on HN