9 ms·

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 th

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 toolchain. Anyway, Vite+ is really just wrapping existing tools into an abstracted command-line interface? And so I have more layers of indirection to wade through in order to get the thing to do what I want? So far I am not optimistic about this prospect...

jackdh 3mo ago
I've followed all the main migrations and I've say they where really quite smooth, can't remember having any major issues and each time it tended to be worth it.
rglover 3mo ago
The churn is the product.
- enraged_camel 3mo ago
  This makes absolutely zero sense. If you're going to post cynically, at least try to have some sort of coherent point?
  - rglover 3mo ago
    Tooling instability creates the demand for more tooling.
    - c-hendricks 3mo ago
      The major change through all of those was solidifying Vite's concepts of "environments" for better SSR support. If you weren't using that, there wasn't much instability. Surely lacking features also creates demand for more tooling.
c-hendricks 3mo ago
Echoing another person, but we did all those major version migrations without any breakage / churn. What were the breaks you ran into?
bhouston 3mo ago
> Version 3 => 4 => 5 => 6 => 7 => 8. I did the migrations and they were not horrible. A few breaking changes but they were relatively isolated. And the speed and improvements over these versions had been quite significant.
Tadpole9181 3mo ago
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?
- volkk 3mo ago
  also i'm pretty sure claude can one shot this these days. a non-issue.
- montroser 3mo ago
  I'm glad that your trivial migration was trivial. All this was a big source of churn for plugins and frameworks: https://github.com/vitejs/vite/discussions/16358 https://github.com/vitejs/vite/discussions/16358
  - c-hendricks 3mo ago
    All those APIs at that point were marked as experimental, and this is the place where things were ironed out. Churn should be expected when using an experimental API.
pier25 3mo ago
> It's not as if it is dramatically better now than it was in version 3 Adding stuff for SSR was a major improvement.
- greatgib 3mo ago
  SSR is a huge pain in the ass. Now it starts to be hard to have all of that do the frontend properly and let good appropriate languages take care of the backend. Instead of a stupid, broken and leaky node equivalent backend totally interlocked with code of the frontend.

jackdh 3mo ago

I've followed all the main migrations and I've say they where really quite smooth, can't remember having any major issues and each time it tended to be worth it.

rglover 3mo ago

The churn is the product.

enraged_camel 3mo ago
This makes absolutely zero sense. If you're going to post cynically, at least try to have some sort of coherent point?
- rglover 3mo ago
  Tooling instability creates the demand for more tooling.
  - c-hendricks 3mo ago
    The major change through all of those was solidifying Vite's concepts of "environments" for better SSR support. If you weren't using that, there wasn't much instability. Surely lacking features also creates demand for more tooling.

c-hendricks 3mo ago

Echoing another person, but we did all those major version migrations without any breakage / churn. What were the breaks you ran into?

bhouston 3mo ago

> Version 3 => 4 => 5 => 6 => 7 => 8. I did the migrations and they were not horrible. A few breaking changes but they were relatively isolated. And the speed and improvements over these versions had been quite significant.

Tadpole9181 3mo ago

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?

volkk 3mo ago
also i'm pretty sure claude can one shot this these days. a non-issue.
montroser 3mo ago
I'm glad that your trivial migration was trivial. All this was a big source of churn for plugins and frameworks: https://github.com/vitejs/vite/discussions/16358 https://github.com/vitejs/vite/discussions/16358
- c-hendricks 3mo ago
  All those APIs at that point were marked as experimental, and this is the place where things were ironed out. Churn should be expected when using an experimental API.

pier25 3mo ago

> It's not as if it is dramatically better now than it was in version 3 Adding stuff for SSR was a major improvement.

greatgib 3mo ago
SSR is a huge pain in the ass. Now it starts to be hard to have all of that do the frontend properly and let good appropriate languages take care of the backend. Instead of a stupid, broken and leaky node equivalent backend totally interlocked with code of the frontend.