They're (usually) not so scary once you figure out how to read them. They might look big and scary, but it's usually just a matter of it getting more and more specific the further down you get. So I usually read the first line, and then go straight to the bottom and figure out the problem. Maybe Harry could make a video on how to read typescript errors. 👍
This is the future that I was looking for in Typescript.
like how can you not love this guy
❤️❤️❤️
u r awesome..man, keep going
Typescript can be scary. Imagine writing typescript code like in 15:55 and then typescript throws one of its vague error messages 😂
They're (usually) not so scary once you figure out how to read them. They might look big and scary, but it's usually just a matter of it getting more and more specific the further down you get. So I usually read the first line, and then go straight to the bottom and figure out the problem. Maybe Harry could make a video on how to read typescript errors. 👍
@@internet4543 of course. Keep digging with a shovel instead of an excavator 😂. I thought the same until I started using ts
`${🤯}` ...You should have started with the cool examples, you almost lost me there...