Avoid These Typescript Mistakes

Подписаться 939 тыс.

Просмотров 10 тыс.

50% 1

💖 Show your support by checking out my courses!
developedbyed.com
-------------------------------------------------------------------------------------------------
Wohoo typescript! Let's talk about how typescript and it's typechecking. What happens at runtime and some common pitfalls devs might run into.
-------------------------------------------------------------------------------------------------
👨‍💻Connect with me
Twitter: / developedbyed
Instagram: / developedbyed
Github: github.com/dev...
-------------------------------------------------------------------------------------------------
🎶 Dope music
C Y G N - Bikini Palm-trees chll.to/d0798a7f
C Y G N - Emotions chll.to/bfeb2b66
C Y G N - Let it go chll.to/41ba6c49
#programming #javascript #typescript

Опубликовано:

26 сен 2024

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист

Посмотреть позже

Комментарии : 35

@developedbyed Год назад

More Typescript? 👀

@mrinaltewary Год назад

Yeah more

@JohnRodDondoyano Год назад

I would be so super happy if you use one of my covers as your bg music while teaching us of more typescript.

@Dazeyy Год назад

I want much more.

@holiqibrahim Год назад

Yeah bro, I need it more

@phaneendra777 Год назад

Sure agre Ed😁

@serpercody5347 Год назад

Great video as always Ed. Honestly you could make a video just talking about anything and I would still watch it, can't wait for more typescript from you.

@dotpenji Год назад

Great job explaining TypeScript concepts! How do you recommend handling API response type inconsistencies to avoid runtime issues?

@motivatedbeastph Год назад

informative content though!

@anonymoussloth6687 Год назад

But why does that first error not get resolved with instanceof? Doesn't typescript have type narrowing?

@mantas9827 11 месяцев назад

Because enemy is an interface not a class. TypeScript interfaces only exist during compile-time for type checking, and they are not present in the resulting JavaScript code after compilation. In the compiled JavaScript, Enemy is not defined, so the instanceof check fails. So to put simply enemy is not a real thing when the code runs, it's just a helpful idea while writing code and therefore the runtime check fails, while in the 'power' in stranger example it's a valid runtime check so everything works.

@Se7en7upp Год назад

hey ed, do you have a typescript course ? a video about it ? Thanks for your amazing work !

@sparshtiwari5485 Год назад

Isn't Svelte and more frameworks switching back to Vanilla JS just because of the complexity that TS has????

@firen777 Год назад

Svelte ditches typescript because they don't want the extra compilation and build step. However, they have plenty of JSDoc typing, which contains most of the Typescript linting/type checking benefits, as well as allowing Typescript use to keep using the framework with no issues. Turbo 8 did it because the author think being a contrarian is a sign of smartness and flipping off contributors is based.

@yajirushik2871 Год назад

copyScript, the world's most advanced programming language which is included in every single of created and already will be with any created in future.