aymericzip/intlayer-skills / skills/intlayer-vanilla
intlayer-vanilla
VerifiedIntegrates Intlayer internationalization with plain JavaScript / TypeScript (no UI framework). Use when the user asks to "setup Vanilla JS i18n", translate a static HTML page, use "useIntlayer" without a framework, or switch locale in a vanilla application.
| File | Kind | Size |
|---|---|---|
| LICENCE.md | markdown | 10.7 KB |
| SKILL.md | skill md | 3.0 KB |
| references/compiler.md | markdown | 14.6 KB |
| references/concept_collections.md | markdown | 5.6 KB |
| references/concept_variants.md | markdown | 20.9 KB |
| references/environment_vanilla.md | markdown | 28.4 KB |
| references/environment_vite-and-vanilla.md | markdown | 39.7 KB |
| references/formatters.md | markdown | 17.3 KB |
| references/packages_intlayer_exports.md | markdown | 12.4 KB |
references/environment_vite-and-vanilla.md
View on GitHub---
createdAt: 2026-03-23
updatedAt: 2026-09-27
priority: 9
title: "Vite + Vanilla JS i18n: Complete Translation Guide"
description: "Set up Intlayer in a Vite app without a framework: translate the DOM, switch locales and keep typed content in .content files."
keywords:
- Internationalization
- Documentation
- Intlayer
- Vite
- Vanilla JS
- JavaScript
- TypeScript
- HTML
slugs:
- doc
- environment
- vite-and-vanilla
applicationTemplate: https://github.com/aymericzip/intlayer-vite-vanilla-template
applicationShowcase: https://intlayer-vite-vanilla.vercel.app
history:
- version: 8.9.0
date: 2026-05-04
changes: "Update Solid useIntlayer API usage to direct property access"
- version: 8.4.10
date: 2026-03-23
changes: "Initial history"
author: aymericzip
---
# Translate your Vite and Vanilla JS website using Intlayer
<Tabs defaultTab="code">
<Tab label="Code" value="code">
<iframe
src="https://ide.intlayer.org/aymericzip/intlayer-vite-vanilla-template?file=intlayer.config.ts"
className="m-auto overflow-hidden rounded-lg border-0 max-md:size-full max-md:h-[700px] md:aspect-16/9 md:w-full"
title="Demo CodeSandbox - Intlayer"
sandbox="allow-forms allow-modals allow-popups allow-presentation allow-same-origin allow-scripts"
loading="lazy"
/>
</Tab>
<Tab label="Demo" value="demo">
<iframe
src="https://intlayer-vite-vanilla.vercel.app"
className="m-auto overflow-hidden rounded-lg border-0 max-md:size-full max-md:h-[700px] md:aspect-16/9 md:w-full"
title="Demo - intlayer-vite-vanilla-template"
sandbox="allow-forms allow-modals allow-popups allow-presentation allow-same-origin allow-scripts"
loading="lazy"
/>
</Tab>
</Tabs>
## Table of Contents
<TOC/>
## Why Intlayer over alternatives?
Compared to main solutions like `i18next` or `i18n.js`, Intlayer is a solution that comes with integrated optimizations such as:
<AccordionGroup>
<Accordion header="Full Vite coverage">
Intlayer is optimized to work perfectly with Vite by offering **framework-agnostic content management**, **TypeScript support**, and all the features needed for scaling internationalization (i18n).
</Accordion>
<Accordion header="Bundle size">
Instead of loading massive JSON files into your pages, load only the necessary content. Intlayer helps **reduce your bundle and page sizes by up to 50%**.
</Accordion>
<Accordion header="Maintainability">
Scoping your application's content **facilitates maintenance** for large-scale applications. You can duplicate or delete a single feature folder without the mental burden of reviewing your entire content codebase. Additionally, Intlayer is **fully typed** to ensure your content's accuracy.
</Accordion>
<Accordion header="AI Agent">
Co-locating content **reduces the context needed** by Large Language Models (LLMs). Intlayer also comes with a suite of tools, such as a **CLI** to test for missing translations,**[LSP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/lsp.md)**, **[MCP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/mcp_server.md)**, and **[agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/agent_skills.md)**, to make the developer experience (DX) even smoother for AI agents.
- [LSP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/lsp.md)
- [MCP](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/mcp_server.md)
- [agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/agent_skills.md)
</Accordion>
<Accordion header="Automation">
Use automation to translate in your CI/CD pipeline using the LLM of your choice at the cost of your AI provider. Intlayer also offers a **compiler** to automate content extraction, as well as a [web platform](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md) to help **translate in the background**.
- [web platform](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md)
</Accordion>
<Accordion header="Performance">
Connecting massive JSON files to components can lead to performance and reactivity issues. Intlayer optimizes your content loading at build time.
</Accordion>
<Accordion header="Scaling with none-dev">
More than just an i18n solution, Intlayer provides an **self-hosted [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md)** and a **[full CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md)** to help you manage your multilingual content in **real-time**, making collaboration with translators, copywriters, and other team members seamless. Content can be stored locally and/or remotely.
- [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md)
- [full CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md)
</Accordion>
</AccordionGroup>
## Step-by-Step Guide to Set Up Intlayer in a Vite and Vanilla JS Application
<Steps>
<Step number={1} title="Install Dependencies">
Install the necessary packages using npm:
```bash packageManager="npm"
npx intlayer init --interactive
```
```bash packageManager="pnpm"
pnpm dlx intlayer init --interactive
```
```bash packageManager="yarn"
yarn dlx intlayer init --interactive
```
```bash packageManager="bun"
bunx intlayer init --interactive
```
> the `--interactive` flag is optional. Use `intlayer-cli init` if you're an AI agent.
> This command will detect your environment and install the required packages. For example:
```bash packageManager="npm"
npm install intlayer vanilla-intlayer
npm install vite-intlayer --save-dev
```
```bash packageManager="pnpm"
pnpm add intlayer vanilla-intlayer
pnpm add vite-intlayer --save-dev
```
```bash packageManager="yarn"
yarn add intlayer vanilla-intlayer
yarn add vite-intlayer --save-dev
```
```bash packageManager="bun"
bun add intlayer vanilla-intlayer
bun add vite-intlayer --dev
```
- **intlayer**
The core package that provides internationalization tools for configuration management, translation, [content declaration](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/content_file.md), transpilation, and [CLI commands](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/index.md).
- **vanilla-intlayer**
The package that integrates Intlayer with plain JavaScript / TypeScript applications. It provides a pub/sub singleton (`IntlayerClient`) and callback-based helpers (`useIntlayer`, `useLocale`, etc.) so any part of your app can react to locale changes without depending on a UI framework.
- **vite-intlayer**
Includes the Vite plugin for integrating Intlayer with the [Vite bundler](https://vite.dev/guide/why.html#why-bundle-for-production), as well as middleware for detecting the user's preferred locale, managing cookies, and handling URL redirection.
</Step>
<Step number={2} title="Configuration of your project">
### Architecture
In this architecture, `vanilla-intlayer` or core `intlayer` provides JavaScript APIs to manage translations and update DOM content dynamically. Content declarations live in `src/`.
```bash
.
├── src
│ ├── app.content.ts
│ ├── counter.ts
│ ├── locale-switcher.ts
│ ├── main.ts # Main script using vanilla-intlayer
│ └── style.css
├── index.html
├── intlayer.config.ts
├── package.json
├── tsconfig.json
└── vite.config.ts
```
### Configuration
Create a config file to configure the languages of your application:
```typescript fileName="intlayer.config.ts" codeFormat={["typescript", "esm", "commonjs"]}
import { Locales, type IntlayerConfig } from "intlayer";
const config: IntlayerConfig = {
internationalization: {
locales: [
Locales.ENGLISH,
Locales.FRENCH,
Locales.SPANISH,
// Your other locales
],
defaultLocale: Locales.ENGLISH,
},
};
export default config;
```
> Through this configuration file, you can set up localized URLs, middleware redirection, cookie names, the location and extension of your content declarations, disable Intlayer logs in the console, and more. For a complete list of available parameters, refer to the [configuration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md).
- [configuration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md)
</Step>
<Step number={3} title="Integrate Intlayer in Your Vite Configuration">
Add the intlayer plugin into your configuration.
```typescript fileName="vite.config.ts" codeFormat={["typescript", "esm", "commonjs"]}
import { defineConfig } from "vite";
import { intlayer } from "vite-intlayer";
// https://vitejs.dev/config/
export default defineConfig({
plugins: [
intlayer({
proxy: {
ignore: (req) => req.url?.startsWith("/api"),
},
}),
],
});
```
> The `intlayer()` Vite plugin is used to integrate Intlayer with Vite. It ensures the building of content declaration files and monitors them in development mode. It defines Intlayer environment variables within the Vite application. Additionally, it provides aliases to optimize performance.
</Step>
<Step number={4} title="Bootstrap Intlayer in your entry point">
Call `installIntlayer()` **before** any content is rendered so that the global locale singleton is ready.
```typescript fileName="src/main.ts" codeFormat="typescript"
import { installIntlayer } from "vanilla-intlayer";
// Must be called before rendering any i18n content.
installIntlayer();
// Import and run your app modules.
import "./app.js";
```
If you also use `md()` content declarations (Markdown), install the markdown renderer as well:
```typescript fileName="src/main.ts" codeFormat="typescript"
import { installIntlayer, installIntlayerMarkdown } from "vanilla-intlayer";
installIntlayer();
installIntlayerMarkdown();
import "./app.js";
```
</Step>
<Step number={5} title="Declare Your Content">
Create and manage your content declarations to store translations:
```typescript fileName="src/app.content.ts" contentDeclarationFormat={["typescript", "esm", "commonjs"]}
import { insert, t, type Dictionary } from "intlayer";
const appContent = {
key: "app",
content: {
title: "Vite + Vanilla",
viteLogoLabel: t({
en: "Vite Logo",
fr: "Logo Vite",
es: "Logo Vite",
}),
count: insert(
t({
en: "count is {{count}}",
fr: "le compte est {{count}}",
es: "el recuento es {{count}}",
})
),
readTheDocs: t({
en: "Click on the Vite logo to learn more",
fr: "Cliquez sur le logo Vite pour en savoir plus",
es: "Haga clic en el logotipo de Vite para obtener más información",
}),
},
} satisfies Dictionary;
export default appContent;
```
```json fileName="src/app.content.json" contentDeclarationFormat="json"
{
"$schema": "https://intlayer.org/schema.json",
"key": "app",
"content": {
"title": "Vite + Vanilla",
"viteLogoLabel": {
"nodeType": "translation",
"translation": {
"en": "Vite Logo",
"fr": "Logo Vite",
"es": "Logo Vite"
}
},
"count": {
"nodeType": "insertion",
"insertion": {
"nodeType": "translation",
"translation": {
"en": "count is {{count}}",
"fr": "le compte est {{count}}",
"es": "el recuento es {{count}}"
}
}
},
"readTheDocs": {
"nodeType": "translation",
"translation": {
"en": "Click on the Vite logo to learn more",
"fr": "Cliquez sur le logo Vite pour en savoir plus",
"es": "Haga clic en el logotipo de Vite para obtener más información"
}
}
}
}
```
> Your content declarations can be defined anywhere in your application as soon as they are included in the `contentDir` directory (by default, `./src`). And match the content declaration file extension (by default, `.content.{json,ts,tsx,js,jsx,mjs,cjs,md,mdx,yaml,yml}`).
>
> For more details, refer to the [content declaration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/content_file.md).
- [content declaration documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/content_file.md)
</Step>
<Step number={6} title="Use Intlayer in Your JavaScript">
`vanilla-intlayer` mirrors the `react-intlayer` surface API: `useIntlayer(key, locale?)` returns the translated content directly. Chain `.onChange()` on the result to subscribe to locale changes - the explicit equivalent of a React re-render.
```typescript fileName="src/main.ts" codeFormat="typescript"
import { installIntlayer, useIntlayer } from "vanilla-intlayer";
installIntlayer();
// Get the initial content for the current locale.
// Chain .onChange() to be notified whenever the locale changes.
const content = useIntlayer("app").onChange((newContent) => {
// Re-render or patch only the affected DOM nodes
document.querySelector<HTMLHeadingElement>("h1")!.textContent = String(
newContent.title
);
document.querySelector<HTMLParagraphElement>(".read-the-docs")!.textContent =
String(newContent.readTheDocs);
});
// Initial render
document.querySelector<HTMLHeadingElement>("h1")!.textContent = String(
content.title
);
document.querySelector<HTMLParagraphElement>(".read-the-docs")!.textContent =
String(content.readTheDocs);
```
> Access leaf values as strings by wrapping them in `String()`, which calls the node's `toString()` method and returns the translated text.
>
> When you need the value for a native HTML attribute (e.g. `alt`, `aria-label`), use `.value` directly:
>
> ```typescript
> img.alt = content.viteLogoLabel.value;
> ```
</Step>
<Step number={7} title="Change the language of your content" isOptional={true}>
To change the language of your content, use the `setLocale` function exposed by `useLocale`.
```typescript fileName="src/locale-switcher.ts" codeFormat="typescript"
import { getLocaleName } from "intlayer";
import { useLocale } from "vanilla-intlayer";
export function setupLocaleSwitcher(container: HTMLElement): () => void {
const { locale, availableLocales, setLocale, subscribe } = useLocale();
const select = document.createElement("select");
select.setAttribute("aria-label", "Language");
const render = (currentLocale: string) => {
select.innerHTML = availableLocales
.map(
(loc) =>
`<option value="${loc}"${loc === currentLocale ? " selected" : ""}>
${getLocaleName(loc)}
</option>`
)
.join("");
};
render(locale);
container.appendChild(select);
select.addEventListener("change", () => setLocale(select.value as any));
// Keep the dropdown in sync when locale changes from elsewhere
return subscribe((newLocale) => render(newLocale));
}
```
</Step>
<Step number={8} title="Render Markdown and HTML content" isOptional={true}>
Intlayer supports `md()` and `html()` content declarations. In vanilla JS, compiled output is inserted as raw HTML via `innerHTML`.
```typescript fileName="src/app.content.ts" contentDeclarationFormat=["typescript", "esm", "cjs"]
import { md, t, type Dictionary } from "intlayer";
const appContent = {
key: "app",
content: {
// ...
editNote: md(
t({
en: "Edit `src/main.ts` and save to test **HMR**",
fr: "Modifiez `src/main.ts` et enregistrez pour tester **HMR**",
es: "Edite `src/main.ts` y guarde para probar **HMR**",
})
),
},
} satisfies Dictionary;
export default appContent;
```
Compile and inject the HTML:
```typescript fileName="src/main.ts" codeFormat="typescript"
import {
compileMarkdown,
installIntlayerMarkdown,
useIntlayer,
} from "vanilla-intlayer";
installIntlayerMarkdown();
const content = useIntlayer("app").onChange((newContent) => {
const el = document.querySelector<HTMLDivElement>(".edit-note")!;
el.innerHTML = compileMarkdown(String(newContent.editNote));
});
document.querySelector<HTMLDivElement>(".edit-note")!.innerHTML =
compileMarkdown(String(content.editNote));
```
> [!TIP]
> `String(content.editNote)` calls `toString()` on the `IntlayerNode` which returns the raw Markdown string. Pass it to `compileMarkdown` to get an HTML string, then set it via `innerHTML`.
> [!WARNING]
> Only use `innerHTML` with trusted content. If the markdown comes from user input, sanitize it first (e.g. with DOMPurify). You can install a sanitizing renderer dynamically:
>
> ```typescript
> import { installIntlayerMarkdownDynamic } from "vanilla-intlayer";
>
> await installIntlayerMarkdownDynamic(async () => {
> const DOMPurify = await import("dompurify");
> return (markdown) => DOMPurify.sanitize(compileMarkdown(markdown));
> });
> ```
</Step>
<Step number={9} title="Add localized Routing to your application" isOptional={true}>
To make unique routes for each language (useful for SEO), you can use `intlayerProxy` in your Vite config for server-side locale detection.
First, add `intlayerProxy` to your Vite config:
> Note that to use `intlayerProxy` in production, you need to move `vite-intlayer` from `devDependencies` to `dependencies`.
> Since Intlayer v9, `intlayerProxy()` is bundled directly into the `intlayer()` plugin and enabled by default through the `routing.enableProxy` option (`true` by default). Registering it separately as shown below is now optional. It is kept for backward compatibility and for setups that need to control plugin order. Set `routing.enableProxy: false` to opt out. See the [v9 release notes](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/releases/v9.md).
- [v9 release notes](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/releases/v9.md)
```typescript {3,7} fileName="vite.config.ts" codeFormat={["typescript", "esm", "commonjs"]}
import { defineConfig } from "vite";
import { intlayer } from "vite-intlayer";
export default defineConfig({
plugins: [
intlayer({
proxy: {
ignore: (req) => req.url?.startsWith("/api"),
},
}),
],
});
```
</Step>
<Step number={10} title="Change the URL when the locale changes" isOptional={true}>
To update the browser URL when the locale changes, call `useRewriteURL()` after installing Intlayer:
```typescript fileName="src/main.ts" codeFormat="typescript"
import { installIntlayer, useRewriteURL } from "vanilla-intlayer";
installIntlayer();
// Rewrites the URL immediately and on every subsequent locale change.
// Returns an unsubscribe function for cleanup.
const stopRewriteURL = useRewriteURL();
```
</Step>
<Step number={11} title="Switch the HTML Language and Direction Attributes" isOptional={true}>
Update the `<html>` tag's `lang` and `dir` attributes to match the current locale for accessibility and SEO.
```typescript fileName="src/main.ts" codeFormat="typescript"
import { getHTMLTextDir } from "intlayer";
import { installIntlayer, useLocale } from "vanilla-intlayer";
installIntlayer();
useLocale({
onLocaleChange: (locale) => {
document.documentElement.lang = locale;
document.documentElement.dir = getHTMLTextDir(locale);
},
});
```
</Step>
<Step number={12} title="Lazy-load dictionaries per locale" isOptional={true}>
For large apps you may want to split each locale's dictionary into its own chunk. Use `useDictionaryDynamic` alongside Vite's dynamic `import()`:
```typescript fileName="src/app.ts" codeFormat="typescript"
import { installIntlayer, useDictionaryDynamic } from "vanilla-intlayer";
installIntlayer();
const unsubscribe = useDictionaryDynamic(
{
en: () => import("../.intlayer/dictionaries/en/app.mjs"),
fr: () => import("../.intlayer/dictionaries/fr/app.mjs"),
es: () => import("../.intlayer/dictionaries/es/app.mjs"),
},
"app"
).onChange((content) => {
document.querySelector("h1")!.textContent = String(content.title);
});
```
> Each locale's bundle is fetched only when that locale becomes active and the result is cached - subsequent switches to the same locale are instant.
</Step>
<Step number={13} title="Extract the content of your components" isOptional={true}>
If you have an existing codebase, transforming thousands of files can be time-consuming.
To ease this process, Intlayer proposes a [compiler](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compiler.md) / [extractor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/extract.md) to transform your components and extract the content.
- [compiler](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compiler.md)
- [extractor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/extract.md)
To set it up, you can add a `compiler` section in your `intlayer.config.ts` file:
```typescript fileName="intlayer.config.ts" codeFormat="typescript"
import { type IntlayerConfig } from "intlayer";
const config: IntlayerConfig = {
// ... Rest of your config
compiler: {
/**
* Indicates if the compiler should be enabled.
*/
enabled: true,
/**
* Defines the output files path
*/
output: ({ fileName, extension }) => `./${fileName}${extension}`,
/**
* Indicates if the components should be saved after being transformed.
*
* - If `true`, the compiler will rewrite the component file in the disk. So the transformation will be permanent, and the compiler will skip the transformation for the next process. That way, the compiler can transform the app, and then it can be removed.
*
* - If `false`, the compiler will inject the `useIntlayer()` function call into the code in the build output only, and keep the base codebase intact. The transformation will be done only in memory.
*/
saveComponents: false,
/**
* Dictionary key prefix
*/
dictionaryKeyPrefix: "",
},
};
export default config;
```
<Tabs>
<Tab value='Extract command'>
Run the extractor to transform your components and extract the content
```bash packageManager="npm"
npx intlayer extract
```
```bash packageManager="pnpm"
pnpm intlayer extract
```
```bash packageManager="yarn"
yarn intlayer extract
```
```bash packageManager="bun"
bun x intlayer extract
```
</Tab>
<Tab value='Babel compiler'>
<Tabs>
<Tab value='intlayer >= 9'>
> Since v9, the `intlayerCompiler` is included in the `intlayer` plugin. So you don't need to add it manually.
</Tab>
<Tab value='intlayer < 9'>
Update your `vite.config.ts` to include the `intlayerCompiler` plugin:
```ts fileName="vite.config.ts"
import { defineConfig } from "vite";
import { intlayer, intlayerCompiler } from "vite-intlayer";
export default defineConfig({
plugins: [
intlayer(),
intlayerCompiler(), // Adds the compiler plugin
],
});
```
</Tab>
</Tabs>
Build your application to transform your components and extract the content
```bash packageManager="npm"
npm run build # Or npm run dev
```
```bash packageManager="pnpm"
pnpm run build # Or pnpm run dev
```
```bash packageManager="yarn"
yarn build # Or yarn dev
```
```bash packageManager="bun"
bun run build # Or bun run dev
```
</Tab>
</Tabs>
</Step>
</Steps>
### (Optional) Sitemap and robots.txt (build-time)
Intlayer includes formatters such as `generateSitemap` and `getMultilingualUrls` that produce crawler-ready multilingual `sitemap.xml` and `robots.txt` output you can write into your project’s `public/` folder. In practice you run a small Node script **before** Vite (for example `predev` / `prebuild` npm hooks) so those files exist when you build or serve the app.
#### Sitemap
Intlayer’s sitemap generator respects your locale setup and includes the usual metadata for crawlers.
> The generated sitemap supports the `xhtml:link` namespace (hreflang XML extensions). Unlike basic generators that only emit flat URLs, Intlayer wires bidirectional links between every localized variant of each page (for example `/about`, `/fr/about`, or `/about?lang=fr`, depending on your routing mode), which helps search engines relate localized URLs.
#### Robots.txt
Use `getMultilingualUrls` so `Disallow` entries cover every localized spelling of sensitive paths.
#### 1. Add `generate-seo.mjs` at the project root
```javascript fileName="generate-seo.mjs"
import fs from "fs";
import path from "path";
import { fileURLToPath } from "url";
import { generateSitemap, getMultilingualUrls } from "intlayer";
const __dirname = path.dirname(fileURLToPath(import.meta.url));
const SITE_URL = (process.env.SITE_URL || "http://localhost:5173").replace(
/\/$/,
""
);
const pathList = [
{ path: "/", changefreq: "daily", priority: 1.0 },
{ path: "/about", changefreq: "monthly", priority: 0.7 },
];
const sitemapXml = generateSitemap(pathList, {
siteUrl: "https://example.com",
});
fs.writeFileSync(path.join(__dirname, "public", "sitemap.xml"), sitemapXml);
const getAllMultilingualUrls = (urls) =>
urls.flatMap((url) => Object.values(getMultilingualUrls(url)));
const disallowedPaths = getAllMultilingualUrls(["/admin", "/private"]);
const robotsTxt = [
"User-agent: *",
"Allow: /",
...disallowedPaths.map((path) => `Disallow: ${path}`),
"",
`Sitemap: https://example.com/sitemap.xml`,
].join("\n");
fs.writeFileSync(path.join(__dirname, "public", "robots.txt"), robotsTxt);
console.log("SEO files generated successfully.");
```
`intlayer` must be installed so the script can import it. Set `SITE_URL` in the environment for production (for example in CI).
> Prefer `generate-seo.mjs` for Node ESM. If you use `generate-seo.js` instead, ensure `"type": "module"` is set in `package.json`, or run Node with ESM enabled.
#### 2. Run the script before Vite
```json fileName="package.json"
{
"scripts": {
"dev": "vite",
"prebuild": "node generate-seo.mjs",
"build": "vite build",
"preview": "vite preview"
}
}
```
Adjust if you use pnpm or yarn. You can also invoke the same script from CI or another step if that fits your workflow.
### Configure TypeScript
Ensure your TypeScript configuration includes the autogenerated types.
```json5 fileName="tsconfig.json"
{
"compilerOptions": {
// ...
},
"include": ["src", ".intlayer/**/*.ts"],
}
```
### Git Configuration
It is recommended to ignore the files generated by Intlayer. This allows you to avoid committing them to your Git repository.
To do this, you can add the following instructions to your `.gitignore` file:
```bash
# Ignore the files generated by Intlayer
.intlayer
```
### VS Code Extension
To improve your development experience with Intlayer, you can install the official **Intlayer VS Code Extension**.
- [Install from the VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=intlayer.intlayer-vs-code-extension)
This extension provides:
- **Autocompletion** for translation keys.
- **Real-time error detection** for missing translations.
- **Inline previews** of translated content.
- **Quick actions** to easily create and update translations.
For more details on how to use the extension, refer to the [Intlayer VS Code Extension documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/vs_code_extension.md).
- [Intlayer VS Code Extension documentation](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/vs_code_extension.md)
### Go Further
To go further, you can implement the [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md) or externalize your content using the [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md).
- [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md)
- [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md)
## Frequently Asked Questions
<FAQ>
<Question title="What are the different solutions available to internationalize a Vite and Vanilla JS app?">
Vite has no opinion on i18n, so the choice comes from the Vanilla JS ecosystem:
- **A hand written dictionary object** imported into your entry point: no dependency, but no typing, no plural rules, and nothing to tell you a translation is missing.
- **`i18next`**: mature and framework agnostic, but it adds a runtime and loads catalogs as JSON.
- **`Intlayer`**: the most advanced solution. Content declared anywhere in your codebase ([next to each component or centralized](https://github.com/aymericzip/intlayer/blob/main/docs/blog/en/per-component_vs_centralized_i18n.md)) and compiled by the Vite plugin at build time, fully typed, with AI translation, a visual editor and a CMS.
The Vite specific gain is that translations are resolved and tree shaken at compile time instead of being fetched as JSON at runtime, so a page ships only the entries it renders. See [why Intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/interest_of_intlayer.md) and the [benchmark](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/benchmark/index.md).
- [why Intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/interest_of_intlayer.md)
- [benchmark](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/benchmark/index.md)
</Question>
<Question title="How much does i18n add to my Vite bundle size?">
Much less than a namespace based setup, because a page never downloads a catalog it does not render. The build time compiler replaces `useIntlayer` calls with the exact dictionary entries a component uses, so unused keys and unused languages are dropped, and [dynamic dictionaries](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dynamic_dictionaries/index.md) split the rest per locale. Measured against the usual alternatives, Intlayer reduces bundle and page size by up to 50%. See [bundle optimization](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/bundle_optimization.md) and the [benchmark](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/benchmark/index.md).
- [dynamic dictionaries](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dynamic_dictionaries/index.md)
- [bundle optimization](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/bundle_optimization.md)
- [benchmark](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/benchmark/index.md)
</Question>
<Question title="Can I migrate from `i18next` without rewriting my modules?">
Largely. Follow the [i18next migration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/migration_from_i18next_to_intlayer.md) to move the content over. You can also migrate gradually: the [sync JSON plugin](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/plugins/sync-json.md) keeps your existing JSON catalogs as the source of truth and generates Intlayer dictionaries from them, so both layers stay in sync while you move modules across one at a time.
- [i18next migration guide](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/migration_from_i18next_to_intlayer.md)
- [sync JSON plugin](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/plugins/sync-json.md)
</Question>
<Question title="Can I keep my existing JSON translation files?">
Yes. The [sync JSON plugin](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/plugins/sync-json.md) keeps your `/messages/{locale}/{namespace}.json` files as the source of truth and generates Intlayer dictionaries from them, in both directions. A [sync PO plugin](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/plugins/sync-po.md) does the same for gettext catalogs, and [per locale files](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/per_locale_file.md) let you split content by language instead of grouping locales in one file.
- [sync JSON plugin](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/plugins/sync-json.md)
- [sync PO plugin](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/plugins/sync-po.md)
- [per locale files](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/per_locale_file.md)
</Question>
<Question title="Do I have to move my content key by key?">
No. Run `npx intlayer extract` and Intlayer reads your components, pulls the user facing strings out and writes a `.content` file next to each one, so you review a diff instead of copying strings into a catalog one at a time. Step 13 of this guide walks through it.
For a fully automated pipeline, the [Intlayer Compiler](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compiler.md) does the same at build time: it scans your JSX, TSX, Vue and Svelte source on every change, generates the dictionaries and keeps them in sync through hot module replacement, so there are no keys to maintain by hand at all.
- [Intlayer Compiler](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/compiler.md)
Two limits are worth knowing before you turn the compiler on. It works by static analysis, so strings that only exist at runtime, such as API error codes or CMS fields, stay out of reach. And it has to tell user facing text apart from application logic like `className="active"` or a status code, which needs a few annotations in a large codebase. The [extract command](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/extract.md) avoids both by keeping you in the loop.
- [extract command](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/extract.md)
</Question>
<Question title="What editor and AI agent tooling is available?">
Five pieces, all optional:
- **[VS Code extension](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/vs_code_extension.md)**: jump from a `useIntlayer` key to the content file that declares it, extract content from a component, and run build, fill, test, push and pull from the command palette or a dedicated Intlayer tab.
- **[LSP server](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/lsp.md)**: the same awareness in any editor that speaks LSP, with go to definition, find all references, hover previews of a translated value, autocompletion of keys and fields, and a warning when a key is not declared anywhere. It also resolves `i18next`, `react-i18next`, `next-intl` and `use-intl` calls, which helps while you migrate.
- **[MCP server](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/mcp_server.md)**: exposes the Intlayer documentation and CLI to Cursor, VS Code, Claude Desktop, Claude Code and ChatGPT, so an assistant answers from current docs instead of guessing, and can run commands such as `intlayer fill` itself.
- **[Agent skills](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/agent_skills.md)**: focused skills such as `intlayer-config`, `intlayer-cli` and `intlayer-content`, plus one per framework, that teach an agent your routing setup and the content node types.
- **[ESLint plugin](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/eslint.md)**: `no-raw-text` flags hardcoded strings, with further rules for static dictionary keys and unused content.
</Question>
<Question title="How do I use translated content in a Vanilla JS component?">
Bootstrap Intlayer in your entry point as step 4 shows, then read the content with `useIntlayer` and write it into the DOM. There is no framework and no virtual DOM involved, so you decide when to update the nodes. Step 8 covers rendering Markdown and HTML content.
</Question>
<Question title="Does Intlayer work with the Vite dev server and hot reload?">
Yes. The `intlayer()` Vite plugin watches your `.content.ts` files and rebuilds the affected dictionaries on save, so edits appear without restarting the dev server, and the generated types are regenerated at the same time so autocompletion stays in sync.
</Question>
<Question title="How do I set up localized routing?">
Steps 9 and 10 cover the localized routes and rewriting the URL when the locale changes. `routing.mode` decides the URL scheme: `"prefix-no-default"` (the default, `/about` and `/fr/about`), `"prefix-all"`, `"no-prefix"` (resolved from a cookie, a header or a domain) or `"search-params"` (`/about?locale=fr`). See the [configuration reference](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md).
- [configuration reference](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/configuration.md)
</Question>
<Question title="How do I support right to left languages such as Arabic or Hebrew?">
Step 11 covers it. `getHTMLTextDir` returns `ltr`, `rtl` or `auto` for a locale, so you bind `lang` and `dir` on the root element from the active locale and let your CSS logical properties handle the rest.
</Question>
<Question title="How do I handle SEO metadata in a client rendered Vite app?">
Set `lang` and `dir` on the `html` element from the active locale, and emit `hreflang` alternates for every declared locale with `getMultilingualUrls`, including `x-default`. For pages that must be crawled reliably, prefer a pre-rendered or server rendered setup.
</Question>
<Question title="How do I translate the app automatically with AI?">
Run `npx intlayer fill`. It fills missing translations with the LLM of your choice, using your own provider and API key, and `--git-diff` limits the run to the content changed on the branch. See the [fill command](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/fill.md) and [CI/CD integration](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/CI_CD.md).
- [fill command](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/cli/fill.md)
- [CI/CD integration](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/CI_CD.md)
</Question>
<Question title="Does Intlayer support plurals, gender and rich text?">
Yes: [plural forms](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/plurial.md), [gender based content](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/gender.md), conditions, [insertions](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/insertion.md), [Markdown](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/markdown.md) and [formatters](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/formatters.md) for numbers, dates and currencies.
- [plural forms](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/plurial.md)
- [gender based content](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/gender.md)
- [insertions](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/insertion.md)
- [Markdown](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dictionary/markdown.md)
- [formatters](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/formatters.md)
</Question>
<Question title="Can I load only the language the visitor needs?">
Yes. Step 12 covers lazy loading dictionaries per locale, so the initial payload carries one language and the others are fetched only if the visitor switches. See [dynamic dictionaries](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dynamic_dictionaries/index.md).
- [dynamic dictionaries](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/dynamic_dictionaries/index.md)
</Question>
<Question title="How can translators edit the content without touching the code?">
Through the [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md), which runs on your own infrastructure and lets anyone edit text in place on the running app, or the [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md), which externalizes content so it can change without a deployment.
- [visual editor](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_visual_editor.md)
- [CMS](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/intlayer_CMS.md)
</Question>
<Question title="Is Intlayer free and open source?">
Yes, under the Apache 2.0 license, commercial use included. The hosted CMS is an optional paid service that can also be [self hosted](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/self_hosting.md).
- [self hosted](https://github.com/aymericzip/intlayer/blob/main/docs/docs/en/self_hosting.md)
</Question>
</FAQ>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |