Migrate from @linguanahq/compiler
Replace the build dependency:
bun remove @linguanahq/compiler
bun add -d @linguanahq/viteThen select the React adapter explicitly:
import { linguana } from "@linguanahq/vite";
import { react as linguanaReact } from "@linguanahq/vite/react";
linguana({
adapter: linguanaReact(),
projectId: "your-project",
token: process.env.LINGUANA_PROJECT_TOKEN,
});environment now defaults to development, sourceLocale defaults to en, and a supplied token enables manifest upload unless upload: false is set. For build-driven translation, replace targetLocales with enabled: true; the dashboard’s enabled Languages list is authoritative.
The compatibility package remains available for one release and emits one deprecation warning per build.
Upgrade to automatic context
Updated compiler integrations emit manifest version 3. Deploy an API and worker version that accepts version 3 before updating SDK/build integrations, and let jobs pinned to the previous prompt version finish before replacing workers.
Automatically generated IDs now identify each usage, so the same words in different UI locations can translate differently. Rebuild, translate, review, and publish catalogs for the new IDs together with the matching app build. Do not remap old translations automatically. Existing published catalogs, explicit t()/<T> identities, and runtime source keys remain compatible.
Editing a heading or label triggers translation for affected nearby messages without changing their IDs. Moving elements or renaming modules can change generated IDs. This may reduce cache reuse and require additional budget for the first upgraded translation run.
Move an existing React or TanStack Start integration to the multi-framework Vite package.
Last updated November 17, 2026
Did this page get you to a working result?