When Not To Use TypeScript

TypeScript is great but sometimes, using it can turn out to be an unnecessary waste of time.

Being a former C# programmer, I’m a big fan of TypeScript and strongly-typed programming languages — having said that, I know better than to use it in every project. In this article, we’ll go through the times where TypeScipt serves its purpose perfectly and other times where using it is an unnecessary waste of time.

TypeScript is good since it might save you a lot of headaches when it comes to debugging your JavaScript during compilation time, but not when you’re using it for the wrong reasons. Like any other tool, to build an app, we need to know first what are the things we have to do before delving deeper in using it.

Want to know when not to use TypeScript? Let us first define what TypeScript is.

Before we do so — a useful tip: Use Bit to encapsulate components with all their dependencies and setup. Build truly modular applications with better code reuse, simpler maintenance and less overhead. Share and collaborate on individual components.

What is TypeScript?

TypeScript is an open-source programming language developed and maintained by Microsoft to act as a superset of JavaScript for checking types during compilation time. It adds optional static typing to the programming language.

Microsoft has designed TypeScript mainly with large applications in mind such as enterprise applications with over 500 users or more. TypeScript can also be used in back-end apps such as NodeJS for strongly-typed language.