offtopic, but I'm in the middle of trying to convince my small team to pick up typescript for a new significant node backend for our company. It seems like a no-brainer from my perspective. Compilation is fast, we would use `strict` but would allow devs to default to `any` if the types got too hard. There are no downsides but so many upsides - better refactoring, intellisense, documentation, communication of interfaces, protection against the javascript and library minefields. Glad to see there are lots of other people thinking this is valuable - wish I could figure out the right way to convince my team.
Diff of the pull request: <a href="https://github.com/facebook/create-react-app/pull/4837/commits/506d1734e02823ad8094ede96a9aa4110381e586" rel="nofollow">https://github.com/facebook/create-react-app/pull/4837/commi...</a>
This is awesome. I recently moved from Typescript to plain Javascript for a project and it is quite frustrating.<p>You don't realise what you had till it's gone!
BTW, anyone here used ReastReason, BuckleScript is it? I've been meaning to look into it but don't have a sense of the payoff. I read that it can coexist which is a great feature. Wonder how it compares to a TypeScript workflow.
I'd love to use TypeScript, but I've hit walls of errors that are nearly as bad as the old C++ template errors! (Though to be fair, this was a while ago, the compiler may have improved).<p>SO: Any <i>good</i> way to learn TypeScript, particularly the more complicated types?