Skip to content

TypeScript

TypeScript, or
fewer bugs in your app

TypeScript is JavaScript with an extra check: before the app reaches users, it verifies that data has the right shape and that the parts of the code fit together. Choose it when the app will be developed for more than a few months or may one day be taken over by another team.

Free 30-minute call · We usually get back to you within a few hours on business days

What TypeScript is and when to choose it

In plain JavaScript some bugs only show up when someone clicks in the wrong place. TypeScript catches many of them while the code is being written: a missing form field, a number stored as text, a function called with the wrong data. For you that means fewer fixes after launch, and code a new developer understands faster because it describes what it expects.

What you gain

  • 01

    Fewer fixes after launch

    Type checking stops many mistakes before they reach the server, so your customers run into fewer errors and new features land more calmly.

  • 02

    Safer changes

    When we change one part of the app, TypeScript shows every place it affects. New work doesn’t break what already works.

  • 03

    Easy to hand over

    The code documents itself, so another team understands it faster. The repository is in your account from day one.

  • 04

    Outside data checked at the door

    Data from forms and other systems is validated as it enters the app, so a wrong format doesn’t break an order or a report.

How we work with TypeScript

We write every web app in strict TypeScript, and type checks run automatically on every change.

  • 01

    While writing

    • Strict type checking from day one
    • Shared types for the database, the server and the interface
    • Validation of data from forms and outside systems
  • 02

    On every change

    • Automatic type checks and tests before deployment
    • A change can’t go in until the checks pass
    • A readable change history in the repository
  • 03

    When taking over a project

    • A gradual move from JavaScript to TypeScript
    • The riskiest areas first
    • Without pausing work on the app

When TypeScript is a good choice

  • An app developed for more than a few months
  • A system with payments, bookings or customer data
  • A project several people work on
  • An app another team will take over one day
  • Old JavaScript code where every change breaks something

When we’d choose something else

  • A one-off prototype to show an idea that will be rebuilt anyway
  • A PrestaShop shop: it runs on PHP, where we use other quality tools
  • A simple site with no logic that you edit in a website builder

See also: React, Node.js

TypeScript in practice

This is how we check code on every change. Your app gets the same process.

Frequently asked questions

Does TypeScript make a project more expensive?
You write a little more code at the start, and it pays back with the first larger changes: fewer bugs to fix and less time spent finding what broke.
Can you convert my app from JavaScript to TypeScript?
Yes, ideally step by step: first the areas where bugs cost the most, such as payments and forms. The app keeps running and evolving in the meantime.
Does TypeScript prevent all bugs?
No. It catches problems with data shapes and with how parts of the code connect, but it doesn’t replace tests or a conversation about how the app should behave. That is why we pair it with tests and a working demo every two weeks.

Does every change to your app break something?

Tell us what is happening. On a call we’ll tell you whether moving to TypeScript would help and where to start.

The button opens a short form: a link or a few sentences is enough. We usually get back to you within a few hours on business days and, if a call would help, suggest a free 30 minutes. You get a written quote for the scope before you decide anything.

See custom software

Prefer to ask first? Email one question about TypeScript to biuro@epko.tech. We usually get back to you within a few hours on business days.

Data stored on EU servers · GDPR-aligned · WCAG 2.1 AA accessibility · You own the code and the copyright