4 ms·

> Hello world may not require CRA, but not using CRA is often a huge mistake. I'd like to learn more about bad times that have occurred due to failure to use

> Hello world may not require CRA, but not using CRA is often a huge mistake. I'd like to learn more about bad times that have occurred due to failure to use CRA up front.

lhorie 6y ago
For example, having to help someone who was stuck for a day debugging a broken setup and it turns out they didn't know class properties are not JS
wayneftw 6y ago
Writing no code and configuring nothing is better than writing code and configuring things. That's more time you get to spend on your actual app. Writing code and configuring things leads to responsibilities and technical debt. So rely on well known, free and easy solutions until you can't. This is the way.
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 ago
  How 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 ago
  Regardless 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 ago
    I 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.

> Hello world may not require CRA, but not using CRA is often a huge mistake. I'd like to learn more about bad times that have occurred due to failure to use CRA up front.

lhorie 6y ago

For example, having to help someone who was stuck for a day debugging a broken setup and it turns out they didn't know class properties are not JS

wayneftw 6y ago

Writing no code and configuring nothing is better than writing code and configuring things. That's more time you get to spend on your actual app. Writing code and configuring things leads to responsibilities and technical debt. So rely on well known, free and easy solutions until you can't. This is the way.

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 ago
How 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 ago
Regardless 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 ago
  I 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.