https://marketplace.visualstudio.com/items?itemName=mohsen1....
[0]: https://raw.githubusercontent.com/s-yadav/react-number-forma...
It cannot be understated how much effort will be put into it. Any moderately sized application with take months of human-hours to get completely switched over.
You'll be wrestling with third-party libraries with meager documentation on how to use with TS, lots of googling to understand how to get the compiler to not complain, and a new build system that has its own idiosyncrasies.
https://github.com/Microsoft/TypeScript/wiki/Type-Checking-J...
I really like typescript. I'm not a static typing fanatic like a lot of people are these days, I prefer the optional annotations approach. You can set the slider to be as loose or as strict as you want, which is amazing. One thing I've just discovered is you can write types like this
type one_to_five = 1 | 2 | 3 | 4 | 5
And it just bloody works.I wish there was a decent REPL for it though. And no, the node REPL or anything based on it is not decent.
Also, probably some React developers would like to use TS/Flow and their manager says 'nope'.
I wish browsers would suck in TS directly. It doesn’t require much translation to get the corresponding JS files, just ignoring some types and that’s it.
It's pretty simple to get TS building via webpack for react, and tsc itself has a watch mode. The only PITA there is if you save any breaking changes, the build will obviously fail until you've completed and saved any the working changes, but at least you can't forget.
Typescript also isn't a very fast compiler, it doesn't seem to be incremental or retained at all, so when you build your project, it take a few seconds when your project has grown beyond a certain size. Sometimes I build and then hit run too early (before the build is actually finished).
Are you doing all of your TS dev in Visual Studio as well?