Setup
Get Vite running
Three steps, no migration. Point it at your project and the first keys land in the dashboard.
- InstallAdd the package or the config block. Nothing else in your build changes.
- Connect your projectUse the org/project identifier from your dashboard. Keys and languages come from there, not from a local file you have to keep in sync.
- ShipPublish once and every locale is a static file on the edge. Copy changes go live without a new deploy.
What it looks like in your code
import { BetterI18nProvider, useTranslations } from '@better-i18n/use-intl'
function App() {
return (
<BetterI18nProvider projectId="your-org/your-project" locale="en">
<Welcome />
</BetterI18nProvider>
)
}
function Welcome() {
const t = useTranslations('home')
return <h1>{t('title')}</h1>
}Surface
What Vite gives you
The exact commands, tools and paths you get. Names are what you type, not marketing labels.
BetterI18nProviderOne provider at the root of your app carries the project and the active locale.
useTranslations(namespace)Read a namespace in any component. Missing keys are visible in development, not silent.
manifest.jsonLanguages are discovered from the project manifest, so adding a locale needs no code change.
cdn.better-i18n.comTranslations are fetched from the edge and updated by publishing, not by redeploying.
Where it fits
How Vite works inside Better
Detect
Pull source strings from your codebase or connect your Vite repository. Keys arrive in Better with structure and context intact.
Review
Run AI translation, assign human reviewers, and gate approval before any change reaches production. Everything auditable in one place.
Ship
Publish to the CDN edge or push translations back to Vite. Copy changes go live without triggering a new app deploy.
Built for modern stacks
Works with the tools your team already uses — fits naturally into CI, review, and edge delivery pipelines without heavy process overhead.
Less operational drift
Centralize translation updates, review sign-off, and delivery in one workflow instead of spreading work across separate tools and scripts.
Controlled rollout
Decouple translation publishing from code releases. Ship copy changes on your schedule without waiting for the next deploy window.
Questions
Before you connect it
Next
Connect Vite today
Free to start. Add the integration, publish once, and see the copy change without a release.