Brining #typescript to our project 2 years ago was a huge mistake
@sorin we've gotten verrryyy long build times. Babel+JS built our project in 2-4 minutes. Brining TS increased it immediately to 7, now it is 14 minutes. We now have to add tiny hacks, like a very handcrafted rules, exclude regexps, include regexpes. Also, TS tends to break compatability. For example, I have a code, which is valid in TS 2.5, but fails with like 40 errors in TS 2.7. Also, we had to bring plugins for webpack, grunt, etc. So adding 1 tool actually added like dozens of pacakges.
@sorin 1 month ago I upgraded webpack to 4.5. It was easy. Then I had to find correct set of packages related to TS, as they do not work well with each others.
For example: https://github.com/s-panferov/awesome-typescript-loader/issues/541
So now we have to upgrade awesome-typescript-loader, which will break other plugins, so we have to upgrade them too...
I can compare to https://reasonml.github.io/ Strong Typed Language ecosystem. It brings 0 webpack plugins, preloaders, babels, etc. It just compiles to JS, then wepback picks files.
@DmytroGladkyi @sorin What is your TS compile time if you just run tsc? I found that some plugins slow down compilation significantly.
@DmytroGladkyi Could you elaborate? What issues did you encounter?