Skip to content
Book a free 30-minute call with an engineer

TypeScript development

Typed JavaScript, used on nearly every project we run.

ZodtRPCPrismaESLintTurborepoNxVitestGraphQL Code Generator

Frontend

Building with TypeScript

Almost everything we build is TypeScript: React and Next.js front ends, Node.js and NestJS APIs, React Native apps. Types catch a whole class of bugs before the code runs, and they make big refactors something you can do on a Tuesday afternoon. On a product that will be maintained for years, it pays for itself within months.

On new projects we turn on strict mode, share types between client and server, and validate data at the edges with Zod. Types only describe what you expect, so anything coming from users or third-party APIs gets checked at runtime too. For existing JavaScript codebases we migrate a file at a time while feature work carries on.

money.tsTypeScript
1type Currency = "USD" | "GBP" | "EUR";​
2​
3export type Money = {​
4 readonly amount: number; // minor units​
5 readonly currency: Currency;​
6};​
7​
8export function add(a: Money, b: Money): Money {​
9 if (a.currency !== b.currency) {​
10 throw new Error("Currency mismatch");​
11 }​
12 return { amount: a.amount + b.amount, currency: a.currency };​
13}​

The kind of TypeScript code our team writes every week.

What we build with TypeScript

  1. 01

    Full-stack TypeScript apps

    The same language from database queries to UI, with the API types shared between both sides.

  2. 02

    JavaScript to TypeScript migration

    File-by-file conversion, tightening compiler settings as we go. Nobody has to stop shipping.

  3. 03

    Type-safe APIs

    End-to-end typed APIs with tRPC, GraphQL Code Generator or clients generated from an OpenAPI spec.

  4. 04

    Monorepo setup

    Turborepo or Nx workspaces that share types, UI and utilities across web, mobile and server.

  5. 05

    Runtime validation

    Zod schemas wherever data enters the system, so bad input fails loudly and early.

  6. 06

    Code quality tooling

    ESLint, a strict tsconfig, type checks in CI and pre-commit hooks.

Why teams pick TypeScript

01

Fewer bugs in production

Type errors show up in the editor and in CI instead of in your error tracker.

02

Refactoring without fear

Rename a field and the compiler lists every line that needs to change.

03

Code that explains itself

Types show what a function expects and returns, which shortens onboarding a lot.

04

One set of types everywhere

Web, mobile and server code can share the same definitions in one repo.

Good fits

  • Large SaaS codebases
  • Shared web and mobile monorepos
  • Public APIs and SDKs
  • Migrating fragile JavaScript apps
  • Financial and data-critical apps

Where we use it

TypeScript questions

Does TypeScript slow development down?

A little in the first week or two, while the core types get defined. After that it's faster: autocomplete works properly, errors show up as you type, and refactors stop being scary. The gain grows with every developer you add to the codebase.

Can we migrate gradually from JavaScript?

Yes. TypeScript and JavaScript files can sit side by side in the same project. We switch TypeScript on, convert the most important modules first and raise the strictness settings over time. Releases keep going the whole way through.

Does TypeScript affect runtime performance?

No. The types are stripped out at build time and what runs is plain JavaScript. Performance is identical to hand-written JavaScript.

Do types replace testing?

No. Types check the shape of your data and how functions are called. Tests check that the business logic does the right thing. A function can be perfectly typed and still calculate the wrong invoice total, so we write both.

Pairs well with