A safety net in the code that flags mismatches as they're written. The mistake gets found while I build — not at eleven at night when someone wants to book.
A typo goes unnoticed until a customer hits a broken page.
Anything that doesn't fit is reported at build time and fixed on the spot.
- Every field has a fixed shape
It's settled that an opening time is text and a price is a number. Mixing them up shows while writing, not in production.
- The check runs before the build
If something doesn't fit, no new version of the site is produced at all. Broken doesn't ship.
- Renaming without fear
When a field gets a new name, the check points at every place that has to follow.
- What ships is ordinary JavaScript
The types disappear at build time. Your site runs plain code.
- Written code
- Check before the build
- Error shown immediately
- Otherwise live
The build stops when something doesn't fit. An error the computer finds is one your customer never sees.
An extension of JavaScript with declared data types. At build time everything is checked for consistency: a misnamed price or a missing translation breaks the build instead of quietly reaching the site. What comes out is ordinary JavaScript.
- Base
- JavaScript
- Checked
- at build time
- Output
- plain JavaScript
- Runtime
- no overhead
Protecting prices, hours and copy against typos
Checking both languages: no page without a translation
Securing forms so no enquiry gets lost
It protects against structural mistakes, not against wrong thinking. A price that is cleanly typed but factually wrong still goes live.
Each of the 30+ pages is checked at build time — a missing translation never reaches the web.