71–80 of 202 posts
Earlier quoted context omitted.
Thanks, that solved it, but now I have other errors like needing to install sass etc. V2 seemed much better now, it just worked, now I have to go installing everything and the kitchen sink. edit: fixed after reading docs. https://vitejs.dev/guide/features.html#css npm add -D sass
Welcome to JS! New upgrade, same problems in new skin, all over again.
> Vite is powering a renewed innovation race in Web frameworks. Wait what, again? I thought we all silently agreed to use the mature/legacy frameworks React and Angular until the proper WASM arrives so that we could burn all of JS/CSS/HTML...
>I thought we all silently agreed to use the mature/legacy frameworks React and Angular until the proper WASM arrives so that we could burn all of JS/CSS/HTML... We did. But people without real problems to solve will continue reinventing the wheel, while we silently churn away on actual products with stable tooling.
Microframeworks are slightly better, especially if they support no-build setups since then a "build step" for prod is only bundling and minification.
Quoted post unavailable.
1. I upgraded a huge application from Vite 2 to Vite 3 with literally no change. 2. Nobody forces you to upgrade, that's how semver works.
This is the second time I've seen this pop up on Hacker News and the second time I've been surprised because it is my last name.
Earlier quoted context omitted.
Vite is framework agnostic. Framework specific work is spearheaded by framework specific community or core authors in some cases (solid, astro) React falters because there are not many community contributing towards react integration. Note: Vite team has done their job for react, but react itself has many concerns particularly due to commonjs that a dedicated person (or team) is needed for react
>Vite is framework agnostic. Framework specific work is spearheaded by framework specific community or core authors in some cases (solid, astro) This is like saying NPM is language agnostic. Sure, technically it is. But we all know what it was built for and what the community is geared toward.
> We decided to release a new Vite major at least every year Isn’t this exhausting? Is it impossible to design good contracts without having to break compatibility every year? In most other language ecosystems it would convey incompetence.
I tried using ESBuild directly for a small web app and it seems pretty nice. What would using Vite on top of it give me?
In my experience, Vite offers a better onboarding process and has a more straightforward configuration format compared to ESBuild. You also get most of rollup's plugin ecosystem and a large amount of community tools made specifically for Vite (Vitest, ViteBook, vite-plugin-pwa, etc...). Also, I might be wrong about this but I don't think ESBuild has HMR, which really speeds up development. Overall, ESBuild feels like…
If I don't write my own build scripts how else am I going to show my coworkers how big brained I am? I need to assert my intellectual superiority somehow...