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
Using vite, we would get a few annoyances out of the way, foremostly the extremely slow build of webpack. It also has its idiosyncratic box of tricks, such as importing static files, sass&jsx out of the box, and hot-reloading much faster than webpack does.
But it has a severe downside: it does not deal (easily) deal with vuetify2, I was not able make that happen do it quickly. Therefore it makes sense to implement this while we move to vue3/vuetify3.
Using vite, we would get a few annoyances out of the way, foremostly the extremely slow build of webpack. It also has its idiosyncratic box of tricks, such as importing static files, sass&jsx out of the box, and hot-reloading much faster than webpack does.
https://vitejs.dev/
The migration to vite is quite simple, I tried it and it took about 30m. I found an awsome guide here: https://qvault.io/javascript/migrating-vue-webpack-to-vitejs/
But it has a severe downside: it does not deal (easily) deal with vuetify2, I was not able make that happen do it quickly. Therefore it makes sense to implement this while we move to vue3/vuetify3.
Another (react oriented) article: https://blog.slashgear.dev/vite-webpack-killer/
The text was updated successfully, but these errors were encountered: