3 ms·
Basically all problems with react end up being a day of debugging. The solutions are never a stack overflow question but are often the nth comment in a github b
by cosmotic 6y ago
Basically all problems with react end up being a day of debugging. The solutions are never a stack overflow question but are often the nth comment in a github bug report. on some obscure dependency your project only indirectly relies on. Deleting node-modules folder and reloading packages is a more-than-monthly occurrence. Manually tweaking package version pins, up and down, explicitly switching sub-dependencies out for newer ones that the maintainer hasn't updated yet, and discovering totally broken and totally replaced dependencies happens constantly. CRA saves you from many of the dependency headaches as it's all pre-pinned, but you still end up fighting all the same battles eventually.
I've never had more dependency hell or build problems with any platform I've used compared to react/npm, which includes Java, .NET, Python, and PHP.
- rimunroe 6y agoHow often do you run into problems like that? I've very rarely encountered anything like that with React, especially in the last two or three years. I don't use create-react-app and my package.json currently lists 88 dependencies.
- JMTQp8lwXL 6y agoRegardless of using CRA or not, would the adoption of a lockfile help in keeping your direct and indirect dependencies pinned to the same versions over time?
- cosmotic 6y agoI experienced these issues with a lock file. Frankly, the dependency manager just isn't doing it's job well. It's job is to manage the dependencies so that I don't have to.