Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Oh man, this brings back nightmares of upgrading jQuery, and third party components that were copy/pasted into the codebase and modified/customized. Large frontend codebases are indeed miles ahead of where they used to be.


The step backwards is that before, you couldn’t upgrade jQuery because the CDN script tag was on thirteen different partials, and you weren’t sure which were still in use, and now you can’t upgrade React because it depends on v4.3.2 of chalk-babel-duster-pack-plugin and that’s insecure but it has a breaking change in v5 you don’t know how to fix, so you’re just waiting for a total rewrite of the app to pull out CRA and replace it with Vite or some such.


There's some kind of law of conservation of complexity. Often we don't solve it, we just move it around or repackage it.


It's called the Waterbed Theory.

https://en.m.wikipedia.org/wiki/Waterbed_theory


Or you can avoid CRA in the first place. CRA is frankly a hot mess. But React itself, and for the most part even Webpack are quite reasonable.


What are your issues with CRA?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: