The Best Ways to Organize and Define your TypeScript Types!

Where should you define your interfaces, enums, etc? Should they be global or should we import each type when needed? In this video, we go over a few best practices for where and when to define those TypeScript types using a simple Node.js Express application.
GitHub Repo: github.com/cov...
Express Template Repo: github.com/cov...
Don't forget to like this video and subscribe to our channel - we're publishing more videos and walkthroughs every week. Comment below and let us know what you'd like to see next!
Join the Covalence community: covalence.io
Shop Covalence merch: covalence.merc...

[@sathishkannan6600]

I would never use .d.ts files as typescript doesn't check these files by default. When we enable checking these files, typescript will scan even node_modules. Better to stick with types.ts files

[@covalence-io]

I've never had an issue with TypeScript not checking them by default. Do you have a tsconfig or no? Also if you're using types for npm packages, those .d.ts files will be in your node_modules @types folder anyway. If you do not want this behavior, I believe you can exclude folders like node_modules from being looked at.

[@gamingbud926]

Spectacular! Thanks for the advice.

[@sadlife7262]

Amazing tutorial! Thanks for sharing this knowledge, i always get a bit confused when thinking about how will i organize the types.

[@covalence-io]

100%! Glad you enjoyed and hope this helps make your projects a little bit easier moving forward :)

[@TypescriptErrorsCentral-hg7hv]

🚀 Tired of banging your head against the wall with TypeScript errors? Look no further than TypescriptErrorsCentral! 🎉 Dive deep into TypeScript & JavaScript errors (even those pesky frameworks!) with crystal-clear examples to squash bugs for good. Perfect for devs of any level! Plus, our community rocks-drop your error message in the comments and let's tackle it together. Don't miss out-subscribe now and kiss those headaches goodbye! 💻✨ #typescript #javascript #programming #errors #coding #devcommunity

[@aniketjadhav2569]

Great advice 👍 thanks.
Can you explain when to use interface and type for reusability

[@covalence-io]

So types can be primitives whereas interfaces cannot, but for the most part, and in all other cases, interfaces should most likely be used over a type. Interfaces provide better type checking capabilities and allow for more thorough errors to be shown at build/compile time. There are a lot of people that feel that types should be used when you're talking about a physical model whereas interfaces should represent an abstract model that many different models can implement, but I tend to disagree with this just a bit. Personally, I tend to think that types should be used when you want a final declaration of a model that you do not want the possibility of extending further (interfaces can be redeclared multiple times and thus the model extended) whereas if you don't mind that aspect, I'd go with an interface.

[@deep_kungch3010]

So helpful thank you😊

[@amranmohamed377]

Can not find namespace models

[@covalence-io]

It's created at the 2min mark

[@cherrycasicas6828]

code gymnastic