> simply npm your webpack via grunt with vue babel or bower to react asdfjkl;lkdhgxdlciuhw Nice summary. While I understand that yarn was a good thing to integrate frontend dependencies management just like we do it for the backend, Webpack is still a mystery to me. Just trying to add a simple JS library to make it work is a headache sometimes (DataTable with Rails for example).
I fought with webpack for years, then ViteJS came out. It works out of the box, is uber fast, support Vue + React and does everything webpack did for me. I stopped thinking about my tooling and could go back to spend those CPU brain cycle on solving my clients problems. Peace of mind. Thanks Evan You.
ViteJS is nothing short of a revelation. Recently migrated all my webapps from webpack5 to vite and it took considerably less time and effort than migrating from webpack 4 to webpack5 did, just removing babeljs reduced the dependency footprint by orders of magnitude. I just had to change a few filename extensions and even though my apps all use a custom react-like, JSX, css-modules, postcss, tailwindcss, d3.js, etc it just worked, I'm still kind of in shock over it. I'm always the one saying "webpack isn't that bad, stop being lazy" but no longer having so many config files and a 1k line package.json polluting project root is a thing of beauty.