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

Vite 8.0 Is Out

vite.dev

Post reply on HN
Print view View original

191–200 of 216 posts

Re: Vite 8.0 Is Out

#191

Post by acemarke »

mexicocitinluez wrote: post #111
drawfloat wrote: post #46

Earlier quoted context omitted.

Vercel has slowly taken over Facebook's position as being the employer of the main developers of React. There's a debate to be had over how much they 'control' it or not, but the fact create-next-app is the first recommended option on the official installation page now does show it's had an impact. 5 or so years ago, Next was a pretty solid option to quickly build up a non SPA, when combined with the static export fu…

> but the fact create-next-app is the first recommended option on the official installation page now does show it's had an impact. There is a decent bit of history around that page and whether some things should go in a collapsible div and whether that was prioritizing certain frameworks over other ones. One thing I'm still salty about is that CRA isn't mentioned anywhere (in the entire site). It's like it never exis…

Hi! I played a major part in getting that "installation" page rewritten to actually mention other tools like Vite :)

The general TLDR is:

- CRA was listed in the _old_ docs site

- The new docs site coincided with the React team emphasizing "frameworks" to provide an all-in-one build experience and hopefully lead to better apps.

- That also meant no ala-carte build tools were listed. This made many people (including me) unhappy.

- CRA broke when React 19 came out in Dec 2024. This caused problems for beginners.

- I pushed the React team to both deprecate CRA and finally rewrite the setup pages to list other build tools as valid options.

I wrote up a much longer background of what happened around the "frameworks" push and this docs page here:

- https://blog.isquaredsoftware.com/2025/06/react-community-20...

And here's the issue I filed pushing the React team to deprecate CRA (after some online discussion):

- https://github.com/facebook/create-react-app/issues/17004

and a follow-up PR where I tried to rewrite the initial rather confusing post-CRA-deprecation "Creating Your Own Framework" page with a more relevant "Creating a React App" page:

- https://github.com/reactjs/react.dev/pull/7618

but the overall point of _all_ of this is that CRA was unmaintained as of 2023, the community had _already_ moved on to Vite, and all this was an attempt to get the React docs to reflect that reality.

Re: Vite 8.0 Is Out

#192

Post by elondaits »

vite_throwaway wrote: post #151
iainmerrick wrote: post #143

Earlier quoted context omitted.

Sorry if this comes across as overly facetious — I’m sure you have a reason for doing it that way! — but would it not be easier just to bow to convention and rename your .js files to .jsx?

Probably. It's just that I've always used .js for my projects (decades). Such a rename would likely result in configuration changes to the other tools I use, but indeed they are better documented. When faced with a multiplicity of conventions I pick one and stick to it; the tools are flexible enough to work with it I'm sure, the real issue is of discoverability.

But it’s not just convention… JSX files are not valid JS files. Also, as a programmer, I would be annoyed to open a JS file and find out it’s actually something else.

Re: Vite 8.0 Is Out

#194

Post by arkon_hn »

Timon3 wrote: post #188
c-hendricks wrote: post #130

Earlier quoted context omitted.

This is great news, but people should also try using regular nodejs import aliases and see if they're viable for their project.

I keep trying the "native" solutions every so often, but every time I quickly hit some snag that makes me question why I'm not just using the solution that actually works. As an example, I just generated a new project using create-vite & added two subpath imports: { // ... "imports": { "#assets/*": "./src/assets/*", "#/*": "./src/*" }, // ... } The second one (#/*) is similar enough to what I usually use (@/*), and i…

You need Typescript 6 for that too: https://devblogs.microsoft.com/typescript/announcing-typescr...

Re: Vite 8.0 Is Out

#195

Post by Klaster_1 »

shunia_huang wrote: post #61

Ah, wondering how long it will take Angular to replace it's sh*t building tool chain to fully vite compatible, hope it could happen before I change may career path or retire.

They recently put out a new roadmap item to adapt the compiler to modern tools: https://angular.dev/roadmap#developer-velocity . Given the great track record of recent Angular road map deliverables, I think they'll come up with something at least faster than what we have now. Angular already runs on Vite, and the fact that Vite 8 exposes AST level plugin endpoints are good signs. Not waiting 1 minute for unit test suite or `ng serve` cold start would be very welcome indeed.

Re: Vite 8.0 Is Out

#196

Post by pjmlp »

drawfloat wrote: post #180
pjmlp wrote: post #51

Earlier quoted context omitted.

My remark, and not complaint, is that the fashion to rewrite everything in Rust across the JavaScript ecosystem proves the point of holding it wrong. Maybe leave JavaScript on the browser, where it belongs.

Rewriting build time tooling to Rust is leaving Javascript on the browser?

Why stop at tbe build tools, take JS ecosystem out of the backend.

Re: Vite 8.0 Is Out

#197

Post by rk06 »

soulchild77 wrote: post #8

Awesome! Too bad Next.js will never profit from these incredible community efforts, because Vercel suffers from NIH.

Vercel owns nuxt and sveltekit, so they do benefit. only nextjs suffers from not being on vite.

Re: Vite 8.0 Is Out

#198

Post by curtisblaine »

ZiiS wrote: post #77
olmo23 wrote: post #62

Earlier quoted context omitted.

If you're already passing over the sources to strip the types, why would you also not do tree-shaking and minifications?

Why would I want to strip my types?

Hear me out: javascript integrates types as comments (ignored by default) in its standard and engines start to use types as performance / optimization hints. If you mistype, your program runs, but you get worse performance and warnings in console. If you type correctly, your program runs more efficiently. We already have different levels of optimization in V8 or JSC, why can't they use type hints to refine predictions?

Re: Vite 8.0 Is Out

#199

Post by flohofwoe »

raydenvm wrote: post #80

Yeah, it makes you wonder how much computing power the industry has wasted over the years on tools that nobody questioned because "that's just how long builds take." We planned our work around it, joked about creating breaks, and built entire caching layers to work around it. Kudos to the Vite maintainers!

No worries, projects will soon catch up by throwing more code at the build system.

Re: Vite 8.0 Is Out

#200

Post by [deleted] »

semiquaver wrote: post #131
raydenvm wrote: post #80

Yeah, it makes you wonder how much computing power the industry has wasted over the years on tools that nobody questioned because "that's just how long builds take." We planned our work around it, joked about creating breaks, and built entire caching layers to work around it. Kudos to the Vite maintainers!

The waste of slow JS bundles is nothing compared to the cost of bloated interpreted runtimes or inefficient abstractions. Most production software is multiple orders of magnitude slower than it needs to be. Just look at all the electron apps that use multiple GB of ram doing nothing and are laggier than similar software written 40 years ago despite having access to an incredibly luxurious amount of resources from any…

[deleted]
Post reply on HN