3 ms·
Good read! I have a huge CRA app I maintain at work, and we've been wanting to migrate to something else for years now. will have to check this out.
by danielhep 2y ago
Good read! I have a huge CRA app I maintain at work, and we've been wanting to migrate to something else for years now. will have to check this out.
- tuyiown 2y agobeware for large apps, if you don't have heavily splitted your app with dynamic imports, vitejs is frustratingly slow by loading each ESM module separately. Seems that rspac has others interesting tradeoffs. Works great once loaded though.
- iliaznk 2y agoWe have encountered that problem too. As far as I learnt from various sources that is caused by circular imports in some cases, and by using index files that re-export your modules in other.
- dangsux 2y ago[dead]
- Vinnl 2y agoIt hasn't been maintained for ages, so at some point you'll want to use some new dependency and find out that you can't. And it's very slow, too, if I recall correctly.
- chrysoprace 2y agoNot OP, but we had issues with SASS that made it difficult to upgrade. It didn't like the M1 architecture when trying to upgrade from Node 12 to Node 18, where as swapping it out for Vite just worked. Given CRA is deprecated, it made sense to move away. I followed a guide[0] which covered most of the things I needed to change and the remaining issues just involved following the build errors. We also saw much-improved build times, which was a welcome change. [0] https://cathalmacdonnacha.com/migrating-from-create-react-app-cra-to-vite https://cathalmacdonnacha.com/migrating-from-create-react-ap...