Hire a TypeScript developer who types the boundaries, not everything

Soham Dang uses TypeScript on production React, Next.js and Node.js codebases, applied where it prevents real failures — API responses, component contracts and shared state — rather than as blanket annotation.

TypeScript pays for itself at boundaries. Inside a function that one person wrote and will rewrite next month, it mostly adds ceremony. At the seam between a server that returns a shape and a client that assumes one, it catches an entire class of bug before it ships.

So the question worth asking of a TypeScript codebase is not how much is typed. It is whether the right things are.

Where the types go

  • API response shapes

    One definition shared between the endpoint and the caller, so a changed field fails the build rather than rendering undefined.

  • Component props

    Composition-friendly types with required and optional cases made explicit, instead of a bag of optional booleans.

  • Shared domain models

    Users, tenants, roles and permissions defined once, so authorisation logic cannot drift between layers.

  • Discriminated unions for state

    Loading, error and success as distinct shapes, which removes the impossible states most bugs live in.

Migrating an existing JavaScript codebase

Incrementally, and from the outside in. Types go on the API layer first, because that is where the highest-value errors are, then on shared models, then on components as they are touched.

A big-bang conversion produces thousands of `any` annotations and a codebase that is typed on paper and unsafe in practice. Converting the seams first gets most of the benefit in a fraction of the work.

The honest limitations

TypeScript checks what your code says about itself. It does not check what the database actually returns, what a third-party API sends on an error path, or what a user pastes into a form.

So runtime validation stays at the edges regardless of how well typed the interior is. Types and validation solve different problems and neither substitutes for the other.

Common questions

Does Soham Dang use TypeScript in production?

Yes. TypeScript is part of his daily stack at Avani Enterprises Ltd. alongside React, Next.js and Node.js, and was used on frontend work at MS Infracon.

Can Soham Dang migrate a JavaScript project to TypeScript?

Yes, incrementally — API layer and shared domain models first, then components as they are touched. That order captures most of the safety benefit without a freeze on feature work.

Is TypeScript worth it on a small project?

At the boundaries, usually yes — typed API responses catch real bugs even in a small codebase. Typing every internal helper on a project one person will finish in a fortnight is usually not worth the friction.