vite

One way that I found out recently in the vite github repository [0], is to use github actions cron job to automatically close issues with certain labels, like "needs reproduction". This way maintainers need to at least explicitly set the label before the issue is closed automatically, and not the other way around. [0]: https://github.com/vitejs/vite/blob/b6d12f71c1dbd5562f25bc2c...

For a beginner, I wouldn't recommend vite just yet. There are still rough edges (like browser load time being unbearably slow): https://github.com/vitejs/vite/issues/3208 If you're starting out, I'd suggest spending more of your time in a higher level of the stack (like writing application code, learning React/etc), rather than spending time deeper down in the plumbing, especially if you're using cutting-edge pieces in the build pipeline.

I literally just spent days trying out Vite and comparing it to Webpack 5, and I can comfortably say that they are in two very distinct leagues. It isn't fair to compare Vite to a CRA build with Webpack. You can greatly improve Webpack's performance by: * Making sure `mode` is set to "development" (don't specify it all if in doubt) * Ditching babel-loader and using esbuild-loader instead * Adjusting build targets and making sure polyfills are not added in development * Making sure you don't import the entirety of libraries like Lodash and MomentJS (prefer date-fns) * [FUTURE] We'll soon be able to tell Webpack to output ES modules just like Vite [1] Vite still has many problems: * It just isn't suitable for proper server-side rendering, we'd need access to chunk names at build time * It has a weird mix of own and Rollup config settings th

Not exactly apples to apples, but I'd like to plug in Vite: https://github.com/vitejs/vite Not that it makes fast minification (which I don't care that much about, I minify only on deploy, and it's a small % of the time it takes), but it does allow for a very fast workflow in dev mode: auto reload seems almost instant even with heavy transpiling. I only mention it because I assume people look at this articles and think about their dev process speed as well. If you haven't, give it a try: it's from the Vue author, so it's really clean, but works with react as well.