Why We Chose TypeScript for Everything (And Why You Probably Should Too)
We resisted TypeScript at first. When you've been writing JavaScript for years, adding types can feel like extra work. But after dealing with a few production issues that types would have caught, we made the switch — and honestly, we should have done it earlier.
TypeScript doesn't just prevent bugs. It makes the codebase easier to understand. When a new dev joins, they can look at types and quickly see what a function expects and what it returns. Less guessing, less time digging around.
We use TypeScript everywhere now: backend with NestJS, frontend with Next.js, and even our shared packages. The consistency is a big deal.
What changed for us
A few things became noticeable after a couple of months:
- Bugs related to mismatched data types dropped a lot.
- Onboarding got faster because the code explains itself better.
- Refactoring stopped feeling like a gamble.
- Shared types kept the frontend and backend aligned.
If you're still on the fence, try it on one project first. Give it a sprint or two. You'll feel the difference.