No disagreement there. It's just so weird to me that there is no "here's how you build an app, here's how you test code, etc" from the big players.
-
-
I think them owning a lot of the top api stack CRA runs on is enough. I see eject as a blessing not a curse, and that mostly due to the support the community has around the chosen stack.
-
I’d love for
@code to have some blessed project setups with typescript. Menu > new typescript project > front end or something -
Samesies.
-
@chancancode and I released libkit and ts-tsd to try to close this gap, fwiw:https://github.com/tildeio/libkit/blob/master/README.md …
End of conversation
New conversation -
-
-
I've never used CRA so I can't really comment :) Setting up React on its own is just not that hard so I never felt the need to check it out. (also I don't set up new React projects often at all so I'm sure that's part of it too)
-
It just means that the sense of stability you're after, where everyone uses the same tools and they get less and less buggy over time, isn't gonna happen on top of CRA. As you said, CRA doesn't even have the vocabulary for why they should care.
-
I'm less after everyone using the same tools, vs, there being fewer options, but they're all solid :) The JS fatigue people are insufferable, but sometimes they have half a point with what a mess things can be on the front end at times.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.