7 Awesome TypeScript Types You Should Know

These have saved me so much time in building out my apps, so I thought I'd share them with you. Hopefully they'll save you just as much time and nerves instead of figuring out all this yourself lol.
Matt Pocock explaining the Prettify Type: • Prettify for Classes
-- my links
Next.js SaaS: www.splitter.gg/
Discord: / discord
GitHub: github.com/joschan21

[@kendanieleramiscal4923]

Another Typescript type, which is not included in the video, is the Pick type, which is the opposite of Omit. Instead of Omitting the property, you include the properties to be picked.

[@sire_ns]

I'll always appreciate these TS videos any day of the week

[@dominikrodler8010]

One of the rare examples where a rather clickbaity sounding video really delivers 👍

[@DevoidFX]

The Prettify type should not exist. It should be a typescript configuration option.

[@maxk5540]

it is good until you are really need to have an object

[@xinaesthetic]

The semantics of what the higher level types are defined as is relevant information.

[@timderks5960]

Man, there's a LOT of information in here I never even heard of, but is pretty much exactly what I need, super cool. This would be a great video to add chapters to btw: 0:00 Intro 0:18 typeof / keyof 1:21 ReturnType / Awaited 2:59 Prettify (and nesting) 4:07 Partial / Required 5:58 Omit / Exclude

[@froxx93]

The exclude util is not necessarily used for more complex types. It's for excluding types from union types in general instead of omitting props from an object type. So you could also use it to exclude e. g. string literals

[@kesoBJJ]

updateTodo example has a bug... you need to prefix fieldsToUpdate with ... if you want to override the todo, otherwise you will create an object with additional fieldsToUpdate property, which contains the values that should be used for updating.

[@Nabulio85]

Great explanations, very well illustrated. Thanks

[@aselivra]

Fantastic video, simple, well explained and to the point. Great examples 👍

[@GambitVil]

Really nice, short but with so many good and important things video.

[@chrise.3114]

Great stuff Josh! Please never stop posting new content!

[@ravinrod]

Wow! These are good TypeScript tips. Thank you!

[@lakhveerchahal]

These are super cool tips. Thank you for sharing them

[@shreyas0924]

We need more videos like these!! Great video buddy

[@rahimco-su3sc]

thanks a lot , we are constantly learning from your videos ! ,keep going

[@Thassalocracy]

I'll never understand why interfaces hide their fields like it's something shameful lol. That Prettify type will save millions of developers including me.

[@julian_handpan]

Bc it’s and interface 😂 not and object…

[@mandokir]

Javascripters trying to understand object orientation.

[@Netrole]

It used to be that way. But people complained that it is confusing and convoluted to see the result of the union when a union of preexisting types is made, instead they wanted to see which types the union is made of.

[@vitvitvitvitvitvitvitvit]

​@@Netrole what hellll. i think would be pretty usefull show the type and your fields. Like: title: string; description: string; role: Role < { name: string, i id: number } >

[@tylim88]

it is useful in creating branded type

[@luccaparadeda1985]

Great video as always

[@njihiamark6926]

great stuff Josh!

[@nidhish6966]

This helped me a lot, Thanks !

[@vorkosiganhs]

Amazing tips!! Thx a lot!

[@carlosricardoziegler2650]

Great content :) I ❤ typescript

[@elliottchong]

Super helpful! Thank you :)

[@solosdev6946]

Thanks Josh helps alot for us :D

[@LeLaboDeHarry]

So useful thank you!

[@petarkolev6928]

Wow! Thanks, Josh 🍻🍻

[@maxwebstudio]

Nice one ! Thanks !

[@TheIpicon]

great video!

[@Leyksnal]

The best thing i have learnt today

[@jagdishpadeliya6050]

Very helpful 🔥

[@JacksonDiKey]

About Exlude is mind-blowing! Tnx

[@raymondmichael4987]

Thanks buddy 😊

[@arifulhaque3236]

That's tips & tricks of Ts is time saving❤

[@akarikev]

awesome pretty helpful!

[@HG-wu6eb]

thank you let God bless you for your kind activity

[@HtetMyat79]

Very greate video thanks

[@matthewbeardsley7004]

Yep, nice!! Thanks heaps!

[@cookieman.19]

This tutorial is valuable

[@vaibhav5783]

This is more complex than learning rust or c or go. Anyway great video :)

[@Renzo-of3yn]

Josh, would be great if you make a video about the skills a junior developer should have to get their first job. THANKS 4 all your content.

[@user-og9np8hp1h]

It is usefull to me thanks!

[@abdulgaffarabdulmalik4333]

Do you mean no matter how nested they are or no matter the number of Joins? Great video btw

[@kilo.ironblossom]

Prettify is now a vscode extension

[@muradmesteliyev5651]

I wonder will you have a video about a project with bun?

[@lanskaba3668]

Our brother always take us from darkness to light . Thank you Josh 🙏

[@ahmedkhairydev]

Great types, you just forgetting `Pick` 👀

Master

[@T25de]

Fuck yea Nice one ☝️

[@latch909]

I’m a bit confused when writing a function in TS aren’t we meant to declare the return type in the function declaration? When would you need to infer the return type??

[@DavidWMiller]

This question is kind of backwards. Why would you want to define it? If you can infer it, the types are done. Your code defined them. Manually defining is redundant extra work. There are cases where you might not want to infer them, but those are the ones you'd need reasons for, which is the opposite of your question.

[@danieljanjanocha7178]

Let’s assume there is a function that returns an array of some kind of ingredients. In useState you want to declare that you want to keep array of some ingredients, but you start with an empty array. How to type the useState without knowing the return type of that function if you don’t wave the type specified elsewhere? It looks like an edge case but I can see a need for it sometimes

[@gnack420]

​@@DavidWMiller no lol, declaring the return type is beneficial because a reader can see what the function returns without having to interpret the function.

[@diegofernandocobacruz6508]

​@@gnack420Typescript shows you the inferred type when hovering the function name. No need for reading the code

[@XxOsirisxX]

@@diegofernandocobacruz6508 The IDE does that, not TypeScript. Open it on a notepad and hover it over.

[@tobiasnickel3750]

I wonder IS prettify could make typescript faster. Maybe not self implemented but As A buildin type. Because of then could avoid looking up complex structures.

[@johnconnor9787]

3:45 Matt Pockock is a TS Ninja. He has a great channel. So as I understand he contributed to TS and created this type?

[@shubhamrawat7895]

type Person = keyof typeof obj type Return = ReturnType Partial Required type Omitted = Omit

[@Ultrajuiced]

5:46 Errr... and what will be the return type of updateTodo again? 😝 Looks like somebody forgot another spread operator: ...fieldsToUpdate

[@meka4996]

I think you can replace all "interface" with "type"

[@LabhamJain]

You should have added Pick as well since you showed omit

[@realQuaz77]

This is not good. We are adding production code to augment IDE assists. I get why it exists, but this is something that should be supported by TS and the tool chain by default.

[@simotasca]

thats true one thing that can be done is "tsc --noEmit --incremental --watch" and that at least shows the errors in the console

[@alasassi5889]

Do u think ai will replace us one day

[@aashiqahmed5273]

prettify is good one

[@manit77]

this is good to know, but you don't need any of this besides making things more complex and harder to debug.

[@sammy709]

The first example doesnt make a lot of sense. Why would you want Person to be either the string literal "name" or "age"

[@IneyeGabriel]

It's just an example probably not the best one. But is super handy when you want to keep track of all keys within an Object or Enum

[@sammy709]

@@IneyeGabriel I know the feature is useful, but the example makes it more confusing

[@laturdaily5110]

ReturnType Awaited Partial Required Omit Exclude

[@JakeAndDaddy]

Good content, but you need to slow down with the delivery. I'm an expert at other languages but only just kept up with it.

[@AlanMeile]

& {} wtf

[@NatoBoram]

Aaaaand the prettify type was fake :/

[@greendsnow]

sorry but this is not a high quality content...

[@allone258]

sorry but this is not a high quality comment

[@juanps2721]

That Prettify type makes the video high quality

[@danieljanjanocha7178]

Like every developer finds a bug once in a while 😂

[@DamirSecki]

can you please, pretty please, extremely please... not pronounce OUR as or and more like hour? (just phonetically like a-uaer, and not o-ur ... I don't know whay is this so annoying to me... but drives me nuts :)