Why YOU should migrate to TypeScript

TypeScript is now the most popular language on GitHub. Learn why everyone's going mad for it.

00:00 Intro
00:29 Undefined is not a function
01:44 Securing your own code
03:07 Libraries
04:38 Third-party API's
05:46 Get out of jail free

Become a TypeScript Wizard with Matt's upcoming TypeScript Course:

Follow Matt on Twitter

[Noway]

I absolutely love TypeScript. Sure i have to type more but that is totally fine with me as long as i know the type of the parameters that I have to pass to a function and the returned value.
Your videos on what one can do with generics are awesome 😀

[johnbull-dev]

5 years working with TypeScript and I don't see why others dislike it. Always good to have some extra checking and helpers.

[davepascual]

I just learned Typescript 2 months recently. From what I learned form it, it made my coding much more fast and predictable especially when I need to know all the possible methods a an object.

[Beastintheomlet]

This comment is to show engagement to the almighty algorithm. Great video and I look forward to more.

[joshuanance]

I'm going to be trying to convince my company to switch to TS soon. Thanks for doing videos like this.

[felipegutierrez]

I love to see TS with React, Solid or any JS framework type save, This content is awesome!

[SahraClayton]

Hi Matt, I am only a beginner in learning Javascript and React, I watch and enjoy your videos as i do find them interesting and you do explain concepts very well. However I get the basics of Typescript like declaring number type in parameters but I have watched your videos and there are things like keyof, extends, T, K, key, generics. it is hard enough to learn Javascript on it's own let alone with all the complicated extra boilerplate

[oneofone_]

Hi Matt
Love the way you teach. Is your course coming this year and how long will it be😁can't wait.
Love from Switzerland

[bideshbanerjee]

In my experience I was really scared to try typescript. But it's just the matter of one project after that there is no looking back to JS....♥️♥️

[MusicRelatedCandy]

Please can you do a video and deconstruct how the types for Express' app.get parses the path params?

[siveroo]

ive been using typescript for 1 year and i loved it. i got my first job last week as a backend dev but they use python and golang. so now i have to move away FROM typescript, and focus to learn those languages instead. feel a little sad but at least i get paid now 😅, anyway man, i love ur typescript stuff, it was really helpful when i was a beginner

[magne]

0:01 Is Wizardry a good thing? Whether in TypeScript or any other kind of programming. Genuinely curious. Because "magic" has been one of the most frequent complaints hurled against programming languages and frameworks for years.

[beatsbycf]

The only time I get errors with typescript is when a package is compiled with the wrong importing implementatiom

[neociber]

I was doing a React test in JS and was a nightmare because typing, I lost 1 hour looking through the src just to understand the fields of an object.

[nabinsaud]

I started using typeScript 3 months ago

[ivanpartida]

Is it possible to get that type inference from the route string when separating the callback function from the router function?

[spitefol]

how would you recommend learning typescript and learning it well, what resources?

[DrWarpMan]

04:38, this is something I struggle to understand when moving onto TypeScript.
If I am not in control of the 3rd Party API. What if they suddenly change the response and the hair_color will be of type number?
Why should I type the response, if I can't guarantee the response will be of that type. Shouldn't I check it via JS anyway?
So you do hair_color: string, but then shouldn't you also do additional checks in your JS code like .. if typeof hair_color === "string" continue, otherwise throw error or something?

[functnal]

What in his VS Code is making the code show up as if its guessing what he's going to type next?

[EdwardTheGreat]

Hey Matt, any particular advice on when to use a text enum vs a union of strings? I like the idea of using an enum where if a value ever needs to change, you don't have to worry about checking for all occurrences, but I find it ends up being a real annoyance when trying to write a type guard at times, where I have to write type predicate functions that confirm it as a member of the enum, rather than TypeScript being able to infer that it's in the enum by matching the strings.