You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Porting the frontend to vite from the current webpack would have many quality of life improvements - you'd get faster development build times, leaner bundles, simpler configuration and its rich plugin ecosystem. In my mind there is no reason to stay on webpack as most new developers start with vite so it won't be a problem to keep maintaining it.
If you're open to the idea I have already implemented it at ManiacMaxo/lago-front and can open a PR for it.
The text was updated successfully, but these errors were encountered:
Thanks for your proposal. We indeed intent to migrate to use Vite. We just needed to find the correct timing between feature development and improvements!
Also IIRC there were one of our Webpack plugging that were either not existing yet for Vite, or useless, and I don't remember which one 😅 .
Of course all contributions are welcome! And we can probably help with that too.
For example we'll make sure this migration does not break our internal deployment scripts for our cloud platform once you opened the PR.
I cannot guarantee our availability during this end of the year period, but we'll look at it for sure :)
Porting the frontend to vite from the current webpack would have many quality of life improvements - you'd get faster development build times, leaner bundles, simpler configuration and its rich plugin ecosystem. In my mind there is no reason to stay on webpack as most new developers start with vite so it won't be a problem to keep maintaining it.
If you're open to the idea I have already implemented it at ManiacMaxo/lago-front and can open a PR for it.
The text was updated successfully, but these errors were encountered: