Use Case
Type-safe i18n that your compiler enforces.
i1n pull generates i1n.d.ts with const assertions for every key. Your IDE autocompletes, your compiler catches missing translations, your deploys never break.
i1n.d.ts
// Auto-generated by i1n pull
export const common = {
greeting: "common.greeting",
errors: {
not_found: "common.errors.not_found",
unauthorized: "common.errors.unauthorized",
},
} as const
// Usage — full autocomplete, compile-time safety
import { t } from 'i1n'
t('common.greeting') // ✓ valid
t('common.typo') // ✗ TypeScript error How i1n solves this
Auto-generated i1n.d.ts
Every i1n pull generates a TypeScript definition file with const assertions. Keys are typed, namespaces are structured, autocomplete just works.
Compile-time validation
If a key doesn't exist in your translations, TypeScript errors at compile time. Missing translations never reach production.
Works with any framework
The generated types work in React, Next.js, Vue, Svelte, and any TypeScript project. No framework lock-in.
Namespace-aware
Types are generated per namespace. Import only the keys your component needs for optimal tree-shaking.
Try it now
Free Starter plan. No credit card required.
More use cases
The localization layer AI agents already...
Your brand voice, in every language...
Automate localization in your CI/CD pipe...
Localize your store for every market....
Localize iOS and Android from one CLI...
Localize your SaaS for every market....
Go global from day one...
Translate .arb files in seconds, not hou...
Translate JSON files with one command....
Translate iOS & macOS .strings files wit...
Translate Android strings.xml with AI....
Translate YAML locale files in seconds....