If you've been using React for a while, you may have noticed times when the freedom and wild nature of JavaScript works against you (and not because of JS 😄). This can be especially true if you're working in a team. You may not know it, but you need TypeScript

freeCodeCamp is a nonprofit organization offering free online coding courses and programming tutorials, covering topics such as web development, data science, and machine learning. Learners can gain practical coding skills, build real-world projects, and earn certifications to advance their careers in tech.

freeCodeCamp

The idea behind this article is to go through the basics of TS and understand the benefits of TypeScript. In the second section of this article, I will cover the specifics of TS with React. This should help you decide if you want those benefits or not.

TypeScript for React Developers – Why TypeScript is Useful and How it Works

Congratulations author, you have an exemplary article!
It is with great joy that I read its content, not only for the quality information but for all the care taken in the way it is delivered.
All the reading pieces of the article composition are linked with visual highlighting for an organic continuity of the reading even when consuming it using accessibility mechanisms. So it is clear that with care such important parts of its composition as keywords that cover a content bias or citation references/source of information of consumption prior to the creation of the article… very well formatted in the ABNT schema.
So I thank you again and that more authors come with such dedication in the creation of content.

The article seems lengthy but its actually a super good, meaningful and pretty crisp introduction to TS. Its not just about the syntax. It covers much more than just explaining the syntax. Its also very personalized, as in the author has amazingly expressed his opinions, POV and thought process. The last section covers its integration with React. It nicely shows with code snippets, how TS can be used with frameworks for more than just static typing/type safety, the regular thing we all hear about TS.
Without the real context based examples (the whys and wherefores as mentioned in the article), typescript always feels like its too much of syntactical overhead for too little benefits.
In fact, I would like to say that using typescript does not mean we have to use it at every possible place.
The trick is to use it to an extent you need it or where it actually reaps benefits. This is very well explained and shown in the article.
One nuanced benefit of declaring types for props I want to highlight even more is that, we can easily indicate which prop is optional. In other words, we can indicate more information about such unsaid things w/o using comments or asking the original developer or reading through the entire logic ourselves.
This improves the dev experience by a lot since we don’t have to completely rely on reading the logic inside the component to figure that info out. Although if the code is poorly written, we can mark a prop as required and write logic in a way that makes it optional but that’s on the dev now and we are safe to assume that devs wont make that blunder.
I believe, that code becomes self documenting from developer’s POV. The interfaces and types speak for themselves.
A thing that author mentioned and I would like to know the reason of, is why to declare function components using function declarations and not expressions.