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

Vite+ Beta

voidzero.dev

Post reply on HN
Print view View original

91–100 of 163 posts

Re: Vite+ Beta

#91

Post by pier25 »

bhouston wrote: post #78
sailorganymede wrote: post #55

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…

Rolldown is used in Vite (non plus) though.

Re: Vite+ Beta

#92

Post by chrisweekly »

Tadpole9181 wrote: post #81
sailorganymede wrote: post #55

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-…

Cloudflare.

Re: Vite+ Beta

#93

Post by jml78 »

mrbombastic wrote: post #74
jml78 wrote: post #32

Earlier quoted context omitted.

I am actually pushing our frontend devs to remove more and more dependencies and leverage LLMs to just write the code instead of all the dumbass packages in hellscape of supply chain attacks via node/npm.

You are signing up for another hellscape of unmaintainable slop. Enable package cooldowns and only whitelist internal packages and you are better off than 90%

You act like the existing packages being published in this ecosystem aren’t already slop or quickly getting there.

We already do cooldowns and disable preinstall and postinstall scripts on all packages except for ones that actually require it.

I bet if you looked at 70% of your dependencies pulled in, you would be horrified. I would rather have that capabilities via code in my repos at this point.

Re: Vite+ Beta

#94

Post by pier25 »

I think they should find a better name for this project. I find it very confusing since it's not really a better Vite.

At the time Void Zero was probably looking to monetize the Vite brand but now that they've been acquired by Cloudflare they don't need to do that anymore.

Re: Vite+ Beta

#95

Post by pier25 »

montroser wrote: post #61

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…

> It's not as if it is dramatically better now than it was in version 3

Adding stuff for SSR was a major improvement.

Re: Vite+ Beta

#96

Post by seanclayton »

alexwebb2 wrote: post #71
ewy1 wrote: post #53

it worked for uv so i can imagine a competent team can do the same thing for javascript!

Surprised to see this is the only uv reference in the comments! Feels like an obvious comparison to me, and a very welcome development for the JS ecosystem. uv made me actually _enjoy_ working in Python again.

a single tool was the enabler of enjoyment? It seems enjoyment is a fleeting thing these days if that's the case

Re: Vite+ Beta

#97

Post by mort96 »

bhouston wrote: post #78
sailorganymede wrote: post #55

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 don't get how a test runner can be "ultra fast". Surely all the time is taken by the tests, not calling the test functions?

Re: Vite+ Beta

#98

Post by mort96 »

beaker52 wrote: post #57
sailorganymede wrote: post #55

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.

This is the latest emerging "boring but works" stack.

"Latest emerging boring but works" sounds like an oxymoron.

Re: Vite+ Beta

#99

Post by moogly »

ivanjermakov wrote: post #18
Cthulhu_ wrote: post #17

Earlier quoted context omitted.

In theory, typescript doesn't need to be transpiled, you can run ts files using `node --experimental-strip-types file.ts` as long as you don't use any code that needs transpilation (like typescript enums). Still need tsx to do type checking

No, because of ESM import resolution rules. Typescript suggests extensionless imports, making it incompartible with ESM and therefore Node. Luckly, `node --import=tsx file.ts` handles imports well. This is especially hairy when making a typescript library that is distributed non-compiled (without dist/) and is supposed to run in both browser and Node. https://github.com/nodejs/node/issues/46006 https://github.com/mic…

I transpile for prod, but use --strip-types when running in dev, and all I had to do was to make a 10-line ESM register hook that rewrites .js to .ts if the .js import fails, and then a one-liner import register trampoline script. Not sure I'd do that in prod, but works fine in dev at least.

This way I could just use node --watch instead of tsx or nodemon.

Re: Vite+ Beta

#100

Post by andrewingram »

mort96 wrote: post #97
bhouston wrote: post #78

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 don't get how a test runner can be "ultra fast". Surely all the time is taken by the tests, not calling the test functions?

At work we've tried switching to vitest, and it's 1.5-2x slower than Jest (I think it's related to our very large and circular module graph), so performance is very much a your-mileage-may-vary thing.
Post reply on HN