Відео

very very thanks for this video.really helpful

that safe zod fetch was amazing! i use zod all the time, but i usually do the parsing manually after a fetch with schemas I have declared in a schemas.ts file

would really appreciate if you could make a generic small course of 10 exercises.

Come on, man! Truthiness doesn't work for the type inference because 0 while being a number is still considered false, so !!member makes no distinction between 0 and null.

With JSX.Element can we do something like JSX.Element<SpecificComponent> to only allow specific react components?

If your large code base has js files that are typed with .d.ts files then surely you want skipLibCheck to be false correct?

Why use any in the Record<string, any> instead of unknown?

People actually use namespace in TypeScript? Can you give us some use cases for namespace (I guess module as well)? Thank you in advance! 🙏

really useful thank you

Simple yet useful solution, thanks!

Video is too fast. No sentence breaks, very difficult to follow.

The idea that redux was ever boiler-plate heavy wa actually never true for any developer who took a little trouble to reduce it. And I still use the "old" versions.

This also means you just reserved MyComponent( or whatever you called it) and it can't be used elsewhere unless you shadow it, not fun if it's Button, I could be wrong though I kinda just guessed it based on what I know

Why not `React.ComponentProps<typeof MyComponent>`?

It worked. Thanks for sharing. But also resulted in an eslint warning @typescript-eslint/no-redeclare

I'm getting kinda imposter syndrome, please explain if we really use such tricky advanced concepts in coding, or is it okay if I'm using simple intermediate level code to get my stuff done, without engaging in fancy stuff like this. Btw, amazing video 🔥🔥!!

You can get 90+% the experience with a non-TS backend too. Just generate your TS client from your backend’s OpenAPI spec

Cool!

similar to as const?

They could have given us a "deepconst" or "fullconst" keyword.

thanks for the video... do you have one where you show how to configure prism with a turborepo ? if not, would you be willing to make a practical video? please?

just use zod

that's a pretty deceiving TS example you took. TS can be really unreadable sometimes. Typescript hasn't really been quite helpfull to me I really tried and found out all it does is slowing me down when I need to ship a product really fast

use option from fp ts

It's funny, I watched this video when it was released, and now I started a new job and we're not using type: "module". Seems like I'm the only one that cares about it.

I got happy for a sec until i saw that .filter(Boolean) still doesn't infer types properly

Never use “as something” in typescript! It is wrong! You need to use const obj = <const>{ . . . }; Because “as” tells typescript to forgot anything about what he knows before and just “shut up and listen what I telling you”

next: let count = 1 // get type: 1 count++ count // get type 2

JavaScript is one big step backwards for mankind

I would love to see an updated video for releasing a npm package. Specificaly, where you also walkthrough how to configure the github actions and getting it completely released. You said nothing about it in this video. There are also a few mistakes in this video, e.g. you never added the release script. Love your videos in general, but would love a better video about this topic

Typescript 5.5 broke global type definitions in our project and we dk how to update 😢

Just use vanilla JS 😂

the question here is whether your ide could find you all the usages when you pass a string instead of an enum value

🤔

seems like using regexes doesn't narrow types down either, e.g. const isAlphaNumeric = (input: string | undefined) => input !== undefined && /^[a-z0-9]+$/i.test(input) won't return `input is string` but just `boolean`

When Matt uploads a new video, we know it’s going to be a new useful knowledge. You’re awesome..❤

But a type guard is absent

What are advantages of namespaces over ComponentProps<T>? Or maybe it's just a curiosity?

so cool, I am new to know React.ComponentProps