TypeScript is great—until it isn’t. After years of using it everywhere, I realized it’s not always the right choice. Here’s why I’ve stopped using TypeScript for small projects. Tagged with javascript, vue, typescript, programming.

Dev.to is a community platform for developers, offering resources, discussions, and networking opportunities to empower individuals in their coding journey. Developers can learn new programming languages, frameworks, and tools, engage in discussions on best practices, and share their experiences with fellow developers to enhance their skills and grow their professional network.

The post explains why TypeScript might be unnecessary for small projects due to the setup overhead, the limitations on experimentation, the relatively lower benefits in small codebases, the extra build step, and compatibility issues with some dependencies. The author's stance is that while TypeScript is beneficial for large-scale applications with multiple developers, for small projects, quick scripts, and MVPs, sticking with JavaScript offers a faster and simpler development experience.

Why Stop Using TypeScript for Small Projects?

3. TypeScript’s Benefits Aren’t That Useful in Small Projects

4. The Extra Build Step Feels Unnecessary

5. Not Every Dependency Plays Nice with TypeScript

Its just a tool! Got tired of articles like : “Why you should/shouldn’t use _______!” and “You should stop/start using ______!”.
Those are tools folks, learn it or reject it, either is fine, no need to rant about it in the form of articles!

“TypeScript is not a religion” - heretic

If you use erasableSyntaxOnly you can run .ts scripts in node directly.
You also don’t have to re-generate a tsconfig file for every single script you make, you can just put your one-off scripts in a folder below the tsconfig in the file hierarchy and it will work just fine.
You can also use JSDoc comments if you want to stay in JS world.
Types and type-checking are very good for intellisense in your code editor of choice, even for tiny scripts.

lol this guy is such drama queen. Points from this article:
<ol>
<li>
The Setup Overhead Isn’t Worth It
<ul>
<li>I get that this might be scary, especially if you don’t understand properly what is going on, but you don’t need to future proof your tsconfig, especially if you are creating MVP.</li>
</ul>
</li>
<li>
TypeScript Slows Down Experimentation
-this guy doesn’t want to write types AND doesn’t want to use :any. No comment, this is purely emotional point.
</li>
<li>
TypeScript’s Benefits Aren’t That Useful in Small Projects
-Any benefit is benefit, no? I personally hate type gymnastics which happens in big projects and I can go on and on about many problems and headaches, you can find something to complain about in every language, in any size of project. While I like ES6, TS offers me more freedom, and when I work on an MVP, I can even allow experimental features which gives me much more freedom than JS offers.
</li>
<li>
The Extra Build Step Feels Unnecessary
<ul>
<li>If you have time to write these ragebait articles, or if I have time complain about those articles, writing extra line in terminal is barely an inconvenience.</li>
</ul>
</li>
<li>
Not Every Dependency Plays Nice with TypeScript
<ul>
<li>Yeah, If I install a package which doesn’t have <a href="https://app.daily.dev/types" data-mention-id="cGT2pHrtSSDXsCJqi1eln" data-mention-username="types" translate="no">@types</a> defined, I won’t have intellisense support so I have to use the package… in same way I’d use it in vanilla JS. No headache needed here, you should get serotonin boost if there is <a href="https://app.daily.dev/types" data-mention-id="cGT2pHrtSSDXsCJqi1eln" data-mention-username="types" translate="no">@types</a> defined as it enables intellisense.</li>
</ul>
</li>
</ol>

That’s definitely a skill issue here, not a typescript one.
While there’s no silver bullet, the arguments presented are too weak to support the claims and instead serves to show how unknowledgeable the author is on the matter.
But I can agree with the fact that someone who presents this many knowledge gaps on certain tech should refrain from using it.
I’m not a Stackoverflow troll or anything, not trying to be rude but I’d rather do my due diligence before trying to lecture the world on how and when to use a tool at the expense of showcasing my own ignorance.
And what’s up with the number of likes? Is it just algorithmic abuse or are we living in a world that ppl really believe and agree with that? Is the typescript community really that infested?