you can write maintainable and easy code in JS, it's not related to the maintainability here.
if you followed the clean code rules and used the right architecture and the right design pattern to solve each problem, you will have maintainable code.
From humble beginnings at an MSP, I've adventured through life as a sysadmin, into an engineer, and finally landed as a developer focused on fixing problems with automation.
Maintainability is basically the reason TypeScript exists. Dynamic typing in large codebases becomes very unwieldy to reason about very quickly. As a webdev primarily in python & js (migrating to TS for aforementioned issues), if I didn't have annotations, I'd go insane.
I said there will always be a debate and there is no right answer, using typescript or not is depends on lots of factors.
how big your project
project estimate time
team knowledge
it's just a different point of view, you will find who really loves and like TS and see it solved a problem and on other side, there will be some people who see that it's useless.
you can write maintainable and easy code in JS, it's not related to the maintainability here.
if you followed the clean code rules and used the right architecture and the right design pattern to solve each problem, you will have maintainable code.
Maintainability is basically the reason TypeScript exists. Dynamic typing in large codebases becomes very unwieldy to reason about very quickly. As a webdev primarily in python & js (migrating to TS for aforementioned issues), if I didn't have annotations, I'd go insane.
I said there will always be a debate and there is no right answer, using typescript or not is depends on lots of factors.
Agreed 100% with the help of JSDoc and good clean architecture Javascript code, no need to add more complexity to your code like TypeScript