| title | Introduction |
|---|---|
| description | Compile-time i18n for JavaScript, TypeScript, React, and beyond |
SayKit is a framework-agnostic internationalisation toolkit built around compile-time message extraction, typed configuration, and small runtime primitives.
You author messages inline with tagged templates or JSX. The saykit CLI extracts them to translation files and compiles each locale into a module of plain data, and a build plugin rewrites your source to small runtime calls. At runtime a view formats those messages with Intl: plurals, ordinals, select, numbers and dates, with nothing left to parse.
import { Braces, WandSparkles, Puzzle, Languages, Boxes, FileType2 } from 'lucide-react';
} title="Author in code" description="Write messages inline with tagged templates or JSX. No keys, no string tables, no juggling translation IDs by hand." /> } title="Compile-time extraction" description="The CLI extracts messages from your source and compiles them ahead of time. Your source stays small and ergonomic." /> } title="ICU MessageFormat" description="Full support for plurals, ordinals, and select using the ICU standard the rest of the i18n world already uses." /> } title="Framework agnostic" description="A small core runtime, plus adapters for React, Next.js, TanStack Start, Carbon, Expo, and anything else with a build plugin." /> } title="Typed config" description="A Zod-validated saykit.config.ts file defines locales, buckets, formatters, and transformers, all under TypeScript." /> } title="Plain translation files" description="Translators work in .po (or your own format). Your app imports the compiled .js beside it: no parser, no loader, no bundler setup." />SayKit wires up like this:
- You author messages with
say`...`or<Say>...</Say>in source files. - The
saykitCLI extracts them into per-locale files (src/locales/en.po,fr.po, …). - Translators (or you) fill in the translations in those files.
- The CLI compiles each locale into a module (
src/locales/fr.js) that your app imports like any other. - At build time a SayKit plugin transforms your source: macros become small
say.call(...)calls. - At runtime,
catalogue.locale(...)returns the locale-boundViewthat formats messages on demand.
There's no SaaS, no proxy, no extra service. Translation files live in your repo, next to the code they describe.
import { Rocket, BookOpen, Boxes as BoxesIcon, Puzzle as PuzzleIcon } from 'lucide-react';
} title="Installation" href="/getting-started/installation" description="Add SayKit to your project for your stack of choice." /> } title="Quickstart" href="/getting-started/quickstart" description="A five-minute end-to-end walkthrough from zero to translated output." /> } title="Architecture" href="/core-concepts/architecture" description="How the runtime, config, transformers, formatters, and plugins fit together." /> } title="Integrations" href="/integrations/react" description="React, Carbon, Vite, Babel, or just the core runtime." />