TypeScript

Three strengths

• Mistakes caught early. TypeScript checks code before it runs. 1 In one academic study, a type checker flagged about 15% of the real bugs it examined, even though testing and review had missed them. 4
• Built for big projects. When a change breaks something elsewhere, TypeScript gives instant feedback while the code is being written, even in very large projects. 1
• Widely used. 43.6% of developers surveyed in 2025 said they use it, so people who know it are easy to find. 5

What it is

Every interactive website runs on JavaScript, a language designed in 1995 for small touches such as a button that reacts when you click it. Today it runs entire applications, and at that size its looseness becomes a risk: in a large project (what developers call a codebase), one change can ripple through hundreds of thousands of files. 1

TypeScript is Microsoft's fix. It's JavaScript with a safety net: you label what each piece of information should be (a name is text, a price is a number), and TypeScript checks that nothing breaks the rules before the software ever runs. 1 Think of it as a spell-checker for code: programmers call these labels types, and the tool that checks them a type checker. In a 2017 academic study of real bugs from public projects, a type checker flagged about 15% of them, even though testing and review had already missed them. 4

The first public release came in October 2012, and version 1.0 followed in April 2014. 2 It was led by Anders Hejlsberg, who also created Turbo Pascal and Delphi, two well-known programming tools. 3 Microsoft was already using it inside its own products; by 2014, one of them held more than 300,000 lines of it. 3 Today it's one of the most used languages in the world, with 43.6% of developers surveyed in 2025 saying they use it. 5

We choose it for the same reason you'd proofread a contract: the cheapest mistake to fix is the one nobody ever sees. For you, that means fewer surprise bugs after launch and an easier hand-over to a new developer, since the labels explain what each piece of the code expects.

How we use it

We build in TypeScript by default. It's the language behind our React and Next.js web apps, and it also runs the behind-the-scenes code on Node.js that connects your systems together.

You'll feel it in two places. In Software Development, it keeps a growing app dependable as we add features. In Integrations & Automations, it helps make sure the data moving between your tools has the shape each one expects, so fewer errors reach your customers and your team.

We use AI-assisted tools to draft code quickly, and TypeScript's checks can catch some of what they get wrong. Once the code is settled, we review it ourselves before it ships to you.

References

1. Microsoft, "Why does TypeScript exist?", typescriptlang.org. https://www.typescriptlang.org/why-create-typescript/ (accessed 28 October 2026)
2. Jonathan Turner, "Announcing TypeScript 1.0", TypeScript Blog, Microsoft, 2 April 2014. https://devblogs.microsoft.com/typescript/announcing-typescript-1-0/ (accessed 28 October 2026)
3. Frederic Lardinois, "Microsoft Adds Full TypeScript Support To Visual Studio", TechCrunch, 25 February 2014. https://techcrunch.com/?p=963576 (accessed 28 October 2026)
4. Zheng Gao, Christian Bird and Earl T. Barr, "To Type or Not to Type: Quantifying Detectable Bugs in JavaScript", Proceedings of the 39th International Conference on Software Engineering (ICSE), 2017, pp. 758 to 769. https://doi.org/10.1109/ICSE.2017.75 (accessed 28 October 2026)
5. Stack Overflow, "2025 Developer Survey: Technology", survey.stackoverflow.co, 2025. https://survey.stackoverflow.co/2025/technology (accessed 28 October 2026)