Skip to content

TypeScript Development

One language and one type system from frontend to database – for code you can change safely.

TypeScript is dectria's standard in new projects – in the React and Next.js frontend, in the Node.js and NestJS backend, in Astro websites and in build and operations tooling. We work in strict mode.

Frontend and backend share types, often in a shared monorepo with pnpm and Turborepo. We additionally validate data that arrives from outside at runtime with Zod, because TypeScript types only exist during development.

We have already migrated existing JavaScript projects to TypeScript step by step, without interrupting operations.

Official website Marc Kornberger Your contact Marc Kornberger Contact for frontend & mobile

What is TypeScript – and when is it worth it?

TypeScript is JavaScript with static types. The compiler checks before execution whether data and functions fit together and then removes the types again – plain JavaScript runs in the browser and on the server.

TypeScript is worth it for practically every application that lives longer than a few weeks or that several people work on: errors surface earlier, and changes can be made safely. It is hardly worth it for one-off scripts and very small prototypes.

Capabilities

What We Build with TypeScript

TypeScript in Strict Mode Generics & Advanced Types Type-Safe API Contracts Shared Types for Frontend & Backend Runtime Validation with Zod Monorepos with pnpm & Turborepo Code Generation from OpenAPI Migration from JavaScript to TypeScript ESLint & Prettier Type-Safe Database Access

Use Cases

Typical Use Cases

Full-Stack Applications in TypeScript

Frontend and backend in one language, with shared types and shared validation, so API changes surface immediately in the frontend.

Type-Safe Interfaces

Types and clients generated from OpenAPI specifications that bind frontend and backend to the same contract.

Migration from JavaScript

Step-by-step migration of existing projects, starting with the most critical modules, without downtime.

References

Projects with TypeScript

Klanglicht Audio Guide
Web Application

Klanglicht - Art Festival of Bühnen Graz

Klanglicht Audio Guide
RRZ Security Handbook
Web Application

Raiffeisen Rechenzentrum (RRZ)

RRZ Security Handbook
RICS Portal
Web Application

Raiffeisen Informatik Center Steiermark (RICS)

RICS Portal
View all references

FAQ

TypeScript FAQ

Why does dectria use TypeScript instead of JavaScript?
Because TypeScript finds many errors before code runs and makes changes in larger codebases safe. Editors show data structures and functions directly, which speeds up onboarding new team members. That is why TypeScript is our standard in new projects.
Can dectria migrate existing JavaScript projects to TypeScript?
Yes, we have done this several times. We migrate step by step: first the configuration, then the most critical modules, then the rest piece by piece. The application keeps running the whole time.
Does TypeScript slow down development?
A little at first, because types have to be written. After that usually not: errors surface earlier, autocompletion saves lookups, and refactorings are safer. The longer a project lives, the more this pays off.
Is TypeScript enough to catch invalid data?
No. TypeScript types only exist during development and are removed at build time. We therefore additionally validate data that arrives from outside at runtime – from forms, APIs or files – with Zod. We derive the types from the same schemas so that validation and types do not drift apart.

Every project starts with a conversation.

Let us talk about your individual needs and goals.

Start a project