Docs / Get started / Quickstart
Vue quickstart
Translate the vue-i18n locale files of your Vue app with verbatra, from install to the first German string on screen.
By the end of this page your Vue app shows a German string that verbatra translated from src/locales/en.json, and a lock file makes every later run translate only what changed. You need Node.js ^22.18.0 || >=24, a Vue project, and about ten minutes. The first four steps need no account and no API key.
Already have locale files and a coding agent? Hand it the prompt on Set up with an AI agent instead: it works around the files your project has and stops before it spends anything.
Steps
Install the CLI
npm install --save-dev @verbatra/cliverbatra is a development tool and never ships in your app. The commands below use npx; with pnpm, yarn, or bun, run pnpm verbatra, yarn verbatra, or bun run verbatra instead.
Add a source locale file
Skip this step if src/locales/en.json already exists. Otherwise create it with two strings, one of them with a placeholder:
{
"greeting": "Hello, {name}!",
"cart": {
"empty": "Your cart is empty."
}
}Scaffold a config
npx @verbatra/cli init --format vue-i18n-json --provider gemini --yes--format vue-i18n-json is the file format of vue-i18n. init finds your locale files, or writes the pattern src/locales/{locale}.json when there are none yet. --yes takes what init detected instead of prompting. The new verbatra.config.ts translates from en into de; add codes to targetLocales for more languages.
Preview the run without a key
npx @verbatra/cli translate --dry-runverbatra: dry run over 1 locale, no provider call
verbatra: de done, 2 would translate
verbatra translate (dry run)
de: 2 would translate, 0 unchanged
1 succeeded, 0 partial, 0 failed (dry run: nothing written)
[ok] dry run done in 0.0s, nothing written
next: verbatra translate (run it for real)A dry run builds no provider, so it needs no key, spends nothing, and writes nothing.
Translate
cp .env.example .envOpen .env and paste your key after GEMINI_. No key yet? Gemini has a free tier: create one in Google AI Studio. Every other provider and its variable is on Providers.
npx @verbatra/cli translateverbatra sends the two strings to Gemini, checks that every placeholder survived, and writes src/locales/de.json. The wording depends on the model, for example:
{
"greeting": "Hallo, {name}!",
"cart": {
"empty": "Dein Warenkorb ist leer."
}
}Check that every locale is in sync
npx @verbatra/cli check[ok] checking the locales (0.0s)
verbatra check
de: 0 missing, 0 stale, 2 up-to-date (in sync)
all locales in synccheck calls no provider and exits 1 once a locale falls out of sync, so it can gate a pull request.
Load the locales in your app
Add vue-i18n:
npm install vue-i18nThen load both files and render the greeting:
import { createApp } from "vue";
import { createI18n } from "vue-i18n";
import App from "./App.vue";
import de from "./locales/de.json";
import en from "./locales/en.json";
const i18n = createI18n({
legacy: false,
locale: "de",
fallbackLocale: "en",
messages: { en, de },
});
createApp(App).use(i18n).mount("#app");<template>
<p>{{ $t("greeting", { name: "Ada" }) }}</p>
</template>Start your app: the greeting reads Hallo, Ada!.
What just happened
verbatra.lock.jsonrecords a hash of each source string, so the next run sends only new and changed strings. See The lock file.- A result that drops a placeholder is withheld, never written. See Translation safety.
Commit the locale files, verbatra.lock.json, and verbatra.provenance.json together.
Optional: connect your coding agent Available from 0.12.0
npx @verbatra/cli init --agentWith the config in place, init --agent keeps it and adds only the agent files: the verbatra rules in AGENTS.md (or CLAUDE.md, when that is your only instruction file) and the verbatra MCP server, with spending off, in the project config of each coding agent it detects. Which files it writes for which agent, and --client to name the agents yourself, are in Set up coding agents. --dry-run shows the files without writing them.
Or, without the CLI, add only the MCP server to your VS Code user profile; use one route, never both:
Next
Add a language
Add a target locale and let one run fill it in.
Run verbatra in CI
Fail a pull request when a locale drifts.
Pick your stack
The format id and file layout for every other framework.