TypeScript for front-end applications that have to last
Strongly typed front-ends where the domain model, the API contract and the components agree with each other, so changes are safe and refactors are boring.
I write TypeScript on every project. On a small site it catches typos. On a large application it is what lets a team change a product model or an API response and find every place that depends on it before a user does.
The value is in the model, not the annotations. I start by typing the domain: what a vessel, a product configuration or a screen layout actually is, and which states are impossible. Components and API clients then follow from those types instead of inventing their own.
What this covers
- Typed domain models and API contracts
- GraphQL schemas as the source of front-end types
- Typed editor extensions and plugin APIs
- Migrating JavaScript codebases to TypeScript
Where I did this
- MB Sports · Klaas Nienhuis Studio · Mirari (2025): A strongly typed product model covering hulls, engines and trim packages, shared across the configuration flow.
- TipTap WYSIWYG for Drupal (2024): Editor chrome written entirely in TypeScript against TipTap's extension API, with each toolbar action as a typed extension.
- Nautical Dashboard (2025): React and TypeScript on a GraphQL gateway that gives multiple legacy systems one consistent API.
- Digital Signage Studio (2025): TypeScript across both the admin editor and the screen player.
- vandeWal-77 · DreamSynth (2026): A polyphonic synthesizer in TypeScript on the WebAudio API, with Web MIDI support.
Related writing
By Guus van de Wal, Senior Front-end Developer & UI Engineer.