Awesome! Too bad Next.js will never profit from these incredible community efforts, because Vercel suffers from NIH.
maybe of interest: https://github.com/cloudflare/vinext
(haven't tried it myself)
Vite 8.0 Is Out
11–20 of 216 posts
Re: Vite 8.0 Is Out
#12Awesome! Too bad Next.js will never profit from these incredible community efforts, because Vercel suffers from NIH.
Got back in to react after a few years’ hiatus and I struggle to even understand what the point of Next is. Bizarrely the official docs even reference Next. Are people using react for non-SPA’s? Why?
Re: Vite 8.0 Is Out
#13> Currently, the Oxc transformer does not support lowering native decorators as we are waiting for the specification to progress Does Oxc also support TS runtime features like constructor parameter properties and enums? I seem to recall in the beta that they had enabled --erasableSyntaxOnly, presumably because Rolldown / Oxc didn't support doing a full transform.
Yes, those work fine: https://playground.oxc.rs/?options=%7B%22run%22%3A%7B%22lint... For that matter, TypeScript's version of decorators ("experimental decorators") also works: https://playground.oxc.rs/?options=%7B%22run%22%3A%7B%22lint... What's not supported is the current draft proposal for standardized ECMAScript decorators; if you uncheck experimentalDecorators, the decorator syntax is simply passed through as…
TC39 decorators emit just landed in tsgo about 24 hours ago. Hopefully they're available in Vite 8 soon. I'm using them in GodotJS https://github.com/godotjs/GodotJS/commit/a4bafef9f14c103b09...
Re: Vite 8.0 Is Out
#14Awesome! Too bad Next.js will never profit from these incredible community efforts, because Vercel suffers from NIH.
They have the enterprise partners that make Next.js the only officially supported SDK on their SaaS integrations.
See Sitecore Cloud, Sanity, Contentful,....
Re: Vite 8.0 Is Out
#15Another rewrite in Rust.
What about finally stop using node.js for server side development?
Re: Vite 8.0 Is Out
#16Re: Vite 8.0 Is Out
#17Another rewrite in Rust. What about finally stop using node.js for server side development?
This is for tooling.
Node.js has been extraordinarily useful for building build tools. We're outgrowing it's capacity and rightfully moving to a compiled language. Also faster tooling is essential for establishing a high quality feedback loop for AI agents
Re: Vite 8.0 Is Out
#18> Built-in tsconfig paths support
A great QoL change. One less place to duplicate (and potentially mistake) a config.
Re: Vite 8.0 Is Out
#19Awesome! Too bad Next.js will never profit from these incredible community efforts, because Vercel suffers from NIH.
They have the enterprise partners that make Next.js the only officially supported SDK on their SaaS integrations. See Sitecore Cloud, Sanity, Contentful,....
Really the enterprise partner supports next, but not vanilla js sounds stupid? Honestly I expect them to prioritize nextjs and react given the popularity, but still be open to vanilla js.
I checked sitecore cloud to have special integration for nextjs and reactjs. But it also support vanilla js as well.
Are there really anyone who is exclusive to nextjs?
Re: Vite 8.0 Is Out
#20Another rewrite in Rust. What about finally stop using node.js for server side development?
This is for tooling. Node.js has been extraordinarily useful for building build tools. We're outgrowing it's capacity and rightfully moving to a compiled language. Also faster tooling is essential for establishing a high quality feedback loop for AI agents
Why go halfway, embrace compiled languages in the backend.
Fast all the way down, especially when coupled with REPL tooling.