The compiler extracts your messages, generates the types and splits bundles per locale. A missing translation fails the build, so it never reaches your users.
Four things the compiler does for you, each one running right here.
One Vite plugin. No giant init(), no Babel macros, no proprietary formats. Catalogs are plain JSON you can take anywhere.
One runtime under every adapter, so the message you write is the same everywhere. Only the package changes.
The text itself declares its params, so if you forget one TypeScript stops you.
No framework? The DOM interpreter hydrates data-verbaly nodes, re-renders on locale switch and watches new elements.
An honest look against the tools you'd otherwise reach for. It shows where Verbaly wins, and where the others are fine too.
| Feature |  Verbaly | i18next | Lingui | Paraglide |
|---|---|---|---|---|
| Type-safe keys & params | Inferred from your text | Plugin / manual | Partial | Yes |
| Runtime size (gzip) | 3.00 KB, zero deps | ~14 KB (+9 KB react) | ~5 KB | ~0 (compiled) |
| Key maintenance | None, auto-extracted | By hand | Extract → compile step | By hand |
| Dynamic / CMS content | Real runtime path | Yes | Yes | Weak |
| Plain HTML (no framework) | DOM interpreter | — | — | — |
| Missing translations | Build fails | Runtime warning | CI step | Build fails |
| Broken translations | Build fails | — | — | — |
| Catalog format | Plain JSON | JSON | PO / JSON | inlang format |
| Coding agents | MCP server + skill | — | Skill | — |
VerbalySizes are approximate gzip runtime footprints; every project weighs trade-offs differently.
Three steps and a guardrail, or let verbaly init scaffold it in one command. No key files written by hand: the compiler does the boring parts while you keep writing product copy.
One command, two packages.
pnpm add verbaly @verbaly/vitePoint it at the locale you write in.
import verbaly from '@verbaly/vite';
export default { plugins: [verbaly({ sourceLocale: 'es' })] };Keys, types and catalogs: generated.
import { t, setLocale } from 'virtual:verbaly';
t`Hola ${name}`; // keys, types & catalogs: generated
await setLocale('pt'); // lazy-loads its chunkExits 1 while any locale is incomplete, so untranslated text never ships.
- run: npx verbaly check # the build gate, in your pipelineSoon you can break it yourself.
A playground on the real runtime: edit the catalogs, switch locales, empty a translation and watch the build gate catch it. It is being built right now.
Read the guide meanwhile