With instantiation expressions, we can now take functions and constructors and feed them type arguments directly.

Consider the following contrived Typescript example: // 1 const hello = (v: String) => { console.log(v) } // 2 const hello = (v: string) => { console.log(v) } Note the difference in the type of the v parameter: string vs String. Don’t use the Object wrapper types As a general rule, you should rarely use

I hate Stackoverflow — said no developer. While it’s helpful to have your answers a Google search away, what’s powerful is truly understanding the solutions you stumble on. In this article, I’ll explore the seven most stackoverflowed Typescript questions. I spent hours researching these. I hope you gain

TLDR: Extend the existing interface declaration for the Window object.

.d.ts files are called type declaration files. They exist for one purpose only: to describe the shape of an existing module and they only contain type information used for type checking.

This is technically called the non-null assertion operator. If the typescript compiler complains that a value could be null or undefined, you can use the ! operator to assert that the said value is NOT null or undefined.

When beginning Typescript, you may find it confusing to settle on a choice. This article clears up the confusion and helps you choose which is right for you.

Hey! 😎 In this detailed (and explanatory) guide, I’ll discuss how to build strongly typed Polymorphic React components with Typescript. If you have no idea what that means, that’s fine. That’s a decent pointer that this is just the right guide for you. Ready? Introduction Let’s get