Live data from Hacker News

Vite+ Beta

voidzero.dev

81–90 of 163 posts

Re: Vite+ Beta

#81

I am a big fan of Vite. But I have zero clue what those other tools are. I swear to God, I just put my head down to do some work and all the sudden, frontend tooling has evolved. I wonder if there is a push towards a "boring but works" stack.

> Vite, Vitest, Rolldown, tsdown, Oxlint, and Oxfmt

You already use the first, the second you should be using and has existed for years - it's a jest-compatible runner integrated to Vite.

Rolldown is a part of Vite already (since version 8, alongside other implementing tools like lightnincss).

The ox* suite are native replacements for eslint and prettier. The latter has existed for years. Both of them aim to be drop-in compatible soon.

This is a boring stack.

FWIR, prior to the purchase by Vercel (or was it Cloud flare?), Vite+ was going to be a convenient, no fuss, low movement way set up projects that they sold to businesses for funding.

Re: Vite+ Beta

#82

Vite had five major version in the four years 2022-2026. Version 3 => 4 => 5 => 6 => 7 => 8. Each one of those had breaking changes and required devs to go through a migration. It's too much. And for what? It's not as if it is dramatically better now than it was in version 3. I can't say I would really look forward to bringing this level of needless churn and constant disruption to the rest of my development toolchai…

I went from 4 to 8 in a single step. I had to change 5 lines of config.

Can we please stop the incessant belly-aching over problems that don't exist. I have to question if you even use these tools?

Re: Vite+ Beta

#83
Extremely happy user of Vite, Vitest, Rolldown, tsdown, Oxlint, and Oxfmt.

I do have lot of hardforked packages, and dont want to look back. Everything just works.

If you confused by the naming, start from Oxlint https://oxc.rs/docs/guide/usage/linter Rolldown https://rolldown.rs/

Did very little changes to tsconfig during past 6 months adoption

My day-to-day process - get the new package unless it some antd6, echart or some rendering engine or geo spatial lib, clean up with Claude, strict and unify type system and align it with my vite, tsconfig, oxlint tastes. The result - no need to follow libs bloat and supply chain attack issues. Easy to read, easy to fix.

Re: Vite+ Beta

#84

I am a big fan of Vite. But I have zero clue what those other tools are. I swear to God, I just put my head down to do some work and all the sudden, frontend tooling has evolved. I wonder if there is a push towards a "boring but works" stack.

A "push" towards a boring stack? That won't happen because the hype cycle trends towards new tools like water down a river. But if you're looking, I can't recommend Rails enough in 2026. Built on web standards, it's quietly pushing the framework forward and is so much less maintenance than modern JS apps.

Re: Vite+ Beta

#85

I am a big fan of Vite. But I have zero clue what those other tools are. I swear to God, I just put my head down to do some work and all the sudden, frontend tooling has evolved. I wonder if there is a push towards a "boring but works" stack.

> But I have zero clue what those other tools are. The incorporated tools are actually really amazing: - vitest, an ultra fast test runner. After using a lot of others, including jest and node's built in one, I love vitest. - oxlint, replaces eslint but is compatible with its file format and ultra fast, since it isn't written JavaScript. I tried biome, but I found oxlint to have more rules and the eslint compatibilit…

I wish Oxfmt supported plugins. Prettier's plugin API is one of the worst APIs I've ever worked with. I'm eager to switch to a different formatter with a better plugin API (and I need plugins).

Re: Vite+ Beta

#86

Earlier quoted context omitted.

> But I have zero clue what those other tools are. The incorporated tools are actually really amazing: - vitest, an ultra fast test runner. After using a lot of others, including jest and node's built in one, I love vitest. - oxlint, replaces eslint but is compatible with its file format and ultra fast, since it isn't written JavaScript. I tried biome, but I found oxlint to have more rules and the eslint compatibilit…

I wish Oxfmt supported plugins. Prettier's plugin API is one of the worst APIs I've ever worked with. I'm eager to switch to a different formatter with a better plugin API (and I need plugins).

Have you tried contributing a system for that?

Re: Vite+ Beta

#87

Vite had five major version in the four years 2022-2026. Version 3 => 4 => 5 => 6 => 7 => 8. Each one of those had breaking changes and required devs to go through a migration. It's too much. And for what? It's not as if it is dramatically better now than it was in version 3. I can't say I would really look forward to bringing this level of needless churn and constant disruption to the rest of my development toolchai…

I went from 4 to 8 in a single step. I had to change 5 lines of config. Can we please stop the incessant belly-aching over problems that don't exist. I have to question if you even use these tools?

also i'm pretty sure claude can one shot this these days. a non-issue.

Re: Vite+ Beta

#88
post #72

Vite had five major version in the four years 2022-2026. Version 3 => 4 => 5 => 6 => 7 => 8. Each one of those had breaking changes and required devs to go through a migration. It's too much. And for what? It's not as if it is dramatically better now than it was in version 3. I can't say I would really look forward to bringing this level of needless churn and constant disruption to the rest of my development toolchai…

The churn is the product.

This makes absolutely zero sense. If you're going to post cynically, at least try to have some sort of coherent point?

Re: Vite+ Beta

#89

I am a big fan of Vite. But I have zero clue what those other tools are. I swear to God, I just put my head down to do some work and all the sudden, frontend tooling has evolved. I wonder if there is a push towards a "boring but works" stack.

> Vite, Vitest, Rolldown, tsdown, Oxlint, and Oxfmt You already use the first, the second you should be using and has existed for years - it's a jest-compatible runner integrated to Vite. Rolldown is a part of Vite already (since version 8, alongside other implementing tools like lightnincss). The ox* suite are native replacements for eslint and prettier. The latter has existed for years. Both of them aim to be drop-…

> This is a boring stack.

I think the boring stack would skip the need for most of these. That is 5 different tools to write TypeScript in order to get some HTML, CSS and JavaScript for things that are not covered by modern web standards. Not including the frameworks itself which mostly have the same goal.

Re: Vite+ Beta

#90

Earlier quoted context omitted.

> But I have zero clue what those other tools are. The incorporated tools are actually really amazing: - vitest, an ultra fast test runner. After using a lot of others, including jest and node's built in one, I love vitest. - oxlint, replaces eslint but is compatible with its file format and ultra fast, since it isn't written JavaScript. I tried biome, but I found oxlint to have more rules and the eslint compatibilit…

I wish Oxfmt supported plugins. Prettier's plugin API is one of the worst APIs I've ever worked with. I'm eager to switch to a different formatter with a better plugin API (and I need plugins).

I was excited about Oxfmt until I tried it and found that it's mostly intended to be a Prettier replacement. Ugh.
Post reply on HN