One could argue that a downside of such a technical stack would be the lack of types – the fact that JavaScript isn’t a strongly typed language. It usually means using a Node.js environment and a server run by the Express library. I know some will say that doing so is really bad, but we have all done it and I am sure we will all continue to do it.A RESTful API in JavaScript can be built from scratch very quickly. In nodejs, more specifically javascript, due to the nature of the language one can fluidly create new properties on objects.

So lets look at a scenario where typescript will make your life a little more difficult, luckily there is a way to get around this problem and continue to enjoy using typescript. I won’t go over why you should use typescript, but there are a couple of situations which will make you think ‘Why did I decide to use Typescript? Arghh!!!' and even that is part of the experience. I believe we have all been in the above mentioned scenario, and that is of course the desired consequence of using typescript. This will undoubtedly push you to create more custom types. I mention tslint just because it will mark all your variables, the ones without an explicit type, as being implicitly typed to any and of course you will get a nice red underline in your IDE or editor. You definitely would have had to create just a few, especially if you are using tslint to check and lint your code. You might have defined several types for your models, or for your function arguments or return types. If you have ever used Express with Typescript you have surely defined new types for your application.

Express typescript