"Some problems may occur in very rare cases" is not a good reason to avoid an entire build system. 11 million downloads per week and only 443 people have upvoted that issue, it's statistically insignificant as far as issues go. I bet I can find Nx issues that have been open for a long time that only affect a few people, but I guess since those issues don't affect you personally, they don't matter?
Who said it didn't affect me personally? I actually had to rewrite two commercial projects from Vite to Webpack because once they went out of PoC phase and started being full-grown apps with more code and more dependencies, build was eating over 4GB of RAM (e.g. that's RAM limit in Bitbucket Pipelines). Webpack? Barely going to 2GB. And for production builds, both of them are similarly slow, because Vite uses Rollup for production builds.
I agree that Vite is very fast for development, but for production builds it's not a viable solution. Angular's team have a nice approach, where they use Vite for development because of speed, and for production they use esbuild. But it depends on the size of the app. If we're talking about small apps, proof of concepts, Vite's great. For large, corporate apps, no.
I guess I the 3 different corporations I worked for where I converted massive react web apps from Webpack to Vite/Rollup must have all missed that problem in all their CI/CD systems for 6 years then. Strange how personal anecdotal evidence works, right?
Why so aggressive? I don't deny what you've written in the article, I even agree that people should stop using CRA. I've just pointed that Vite may not always be reliable, based on my own experience, and backed with a GitHub issue with over 400 likes. I'm glad that you didn't have any problems with Vite and I wish I also had the same experience.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"Some problems may occur in very rare cases" is not a good reason to avoid an entire build system. 11 million downloads per week and only 443 people have upvoted that issue, it's statistically insignificant as far as issues go. I bet I can find Nx issues that have been open for a long time that only affect a few people, but I guess since those issues don't affect you personally, they don't matter?
Who said it didn't affect me personally? I actually had to rewrite two commercial projects from Vite to Webpack because once they went out of PoC phase and started being full-grown apps with more code and more dependencies, build was eating over 4GB of RAM (e.g. that's RAM limit in Bitbucket Pipelines). Webpack? Barely going to 2GB. And for production builds, both of them are similarly slow, because Vite uses Rollup for production builds.
I agree that Vite is very fast for development, but for production builds it's not a viable solution. Angular's team have a nice approach, where they use Vite for development because of speed, and for production they use esbuild. But it depends on the size of the app. If we're talking about small apps, proof of concepts, Vite's great. For large, corporate apps, no.
I guess I the 3 different corporations I worked for where I converted massive react web apps from Webpack to Vite/Rollup must have all missed that problem in all their CI/CD systems for 6 years then. Strange how personal anecdotal evidence works, right?
Why so aggressive? I don't deny what you've written in the article, I even agree that people should stop using CRA. I've just pointed that Vite may not always be reliable, based on my own experience, and backed with a GitHub issue with over 400 likes. I'm glad that you didn't have any problems with Vite and I wish I also had the same experience.