Ask your question and get a summary of the document by referencing this page and the AI provider of your choice
Version History
- "Update Solid useIntlayer API usage to direct property access"v8.9.004/05/2026
- "Add init command"v7.5.930/12/2025
- "Initial history"v5.5.1029/06/2025
The content of this page was translated using an AI.
See the last version of the original content in EnglishIf you have an idea for improving this documentation, please feel free to contribute by submitting a pull request on GitHub.
GitHub link to the documentationCopy doc Markdown to clipboard
Getting Started Internationalising (i18n) with Intlayer and Vite and Solid
Table of Contents
Why Intlayer over alternatives?
Compared to main solutions like @solid-primitives/i18n or i18next, Intlayer is a solution that comes with integrated optimizations such as:
Intlayer is optimized to work perfectly with Solid by offering component-level content scoping, reactive translations, and all the features needed for scaling internationalization (i18n).
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%.
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.
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, MCP, and agent skills, to make the developer experience (DX) even smoother for AI agents.
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 to help translate in the background.
Connecting massive JSON files to components can lead to performance and reactivity issues. Intlayer optimizes your content loading at build time.
More than just an i18n solution, Intlayer provides an self-hosted visual editor and a full CMS 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.
Step-by-Step Guide to Set Up Intlayer in a Vite and Solid Application
Table of Contents
Install Dependencies
Install the necessary packages using npm:
bashCopy codeCopy the code to the clipboard
the
--interactiveflag is optional. Useintlayer-cli initif you're an AI agent.This command will detect your environment and install the required packages. For example:
bashCopy codeCopy the code to the clipboard
intlayer
The core package that provides internationalisation tools for configuration management, translation, content declaration, transpilation, and CLI commands.
solid-intlayer The package that integrates Intlayer with Solid applications. It provides context providers and hooks for Solid internationalisation.
vite-intlayer Includes the Vite plugin for integrating Intlayer with the Vite bundler, as well as middleware for detecting the user's preferred locale, managing cookies, and handling URL redirection.
Configuration of your project
Create a config file to configure the languages of your application:
intlayer.config.tsCopy codeCopy the code to the clipboard
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 localised 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.
Integrate Intlayer into Your Vite Configuration
Add the intlayer plugin to your configuration.
vite.config.tsCopy codeCopy the code to the clipboard
import { defineConfig } from "vite"; import react from "@vitejs/plugin-react-swc"; import { intlayer } from "vite-intlayer"; // https://vitejs.dev/config/ export default defineConfig({ plugins: [react(), intlayer()], });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 optimise performance.Declare Your Content
Create and manage your content declarations to store translations:
src/app.content.tsxCopy codeCopy the code to the clipboard
import { t, type Dictionary } from "intlayer"; const appContent = { key: "app", content: {}, } satisfies Dictionary; export default appContent;Your content declarations can be defined anywhere in your application as soon as they are included in the
contentDirdirectory (by default,./src). And match the content declaration file extension (by default,.content.{json,ts,tsx,js,jsx,mjs,cjs,md,mdx,yaml,yml}).Utilise Intlayer in Your Code
Access your content dictionaries throughout your application:
src/App.tsxCopy codeCopy the code to the clipboard
In Solid,
useIntlayerreturns an accessor function (e.g., `content.). You must call this function to access the reactive content.If you want to use your content in a
stringattribute, such asalt,title,href,aria-label, etc., you can use the value of the function, like:htmlCopy codeCopy the code to the clipboard
Change the language of your content
OptionalTo change the language of your content, you can use the
setLocalefunction provided by theuseLocalehook. This function allows you to set the locale of the application and update the content accordingly.src/components/LocaleSwitcher.tsxCopy codeCopy the code to the clipboard
Add localised Routing to your application
OptionalThe purpose of this step is to make unique routes for each language. This is useful for SEO and SEO-friendly URLs. Example:
plaintextCopy codeCopy the code to the clipboard
To add localised routing to your application, you can use
@solidjs/router.First, install the necessary dependencies:
bashCopy codeCopy the code to the clipboard
Then, wrap your application with the
Routerand define your routes usinglocaleMap:src/index.tsxCopy codeCopy the code to the clipboard
src/App.tsxCopy codeCopy the code to the clipboard
Change the URL when the locale changes
OptionalTo change the URL when the locale changes, you can use the
onLocaleChangeprop provided by theuseLocalehook. You can use theuseNavigateanduseLocationhooks from@solidjs/routerto update the URL path.src/components/LocaleSwitcher.tsxCopy codeCopy the code to the clipboard
Switch the HTML Language and Direction Attributes
OptionalUpdate the
<html>tag'slanganddirattributes to match the current locale for accessibility and SEO.src/App.tsxCopy codeCopy the code to the clipboard
Creating a Localised Link Component
OptionalCreate a custom
Linkcomponent that automatically prefixes internal URLs with the current language.src/components/Link.tsxCopy codeCopy the code to the clipboard
In parallel, you can also use the
intlayerProxyto add server-side routing to your application. This plugin will automatically detect the current locale based on the URL and set the appropriate locale cookie. If no locale is specified, the plugin will determine the most appropriate locale based on the user's browser language preferences. If no locale is detected, it will redirect to the default locale.Note that to use the
intlayerProxyin production, you need to switch thevite-intlayerpackage fromdevDependenciestodependencies.Since Intlayer v9,
intlayerProxy()is bundled directly into theintlayer()plugin and enabled by default through therouting.enableProxyoption (trueby 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. Setrouting.enableProxy: falseto opt out. See the v9 release notes.vite.config.tsCopy codeCopy the code to the clipboard
Render Markdown
OptionalIf you have an existing codebase, transforming thousands of files can be time-consuming.
To ease this process, Intlayer propose a compiler / extractor to transform your components and extract the content.
Intlayer supports rendering Markdown content directly in your Solid application using its own internal parser. By default, Markdown is treated as plain text. To render it as rich HTML, wrap your application with the
MarkdownProvider.src/index.tsxCopy codeCopy the code to the clipboard
Run the extractor to transform your components and extract the content
bashCopy codeCopy the code to the clipboard
Then you can use it in your components:
Since v9, the
intlayerCompileris included in theintlayerplugin. So you don't need to add it manually.Update your
vite.config.tsto include theintlayerCompilerplugin:tsxCopy codeCopy the code to the clipboard
bashCopy codeCopy the code to the clipboard
(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 thexhtml:linknamespace (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
Copy the code to the clipboard
intlayer must be installed so the script can import it. Set SITE_URL in the environment for production (for example in CI).
Prefergenerate-seo.mjsfor Node ESM. If you usegenerate-seo.jsinstead, ensure"type": "module"is set inpackage.json, or run Node with ESM enabled.
2. Run the script before Vite
Copy the code to the clipboard
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.
Copy the code to the clipboard
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:
Copy the code to the clipboard
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
Go Further
To go further, you can implement the visual editor or externalise your content using the CMS.
Frequently Asked Questions
Vite has no opinion on i18n, so the choice comes from the Solid ecosystem:
@solid-primitives/i18n: the community primitive, a flat dictionary you assemble and load yourself.i18nextwith a Solid wrapper: mature catalogues, but no reactivity story of its own.Intlayer: the most advanced solution. Content declared anywhere in your codebase (next to each component or centralized) 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 and the benchmark.
Much less than a namespace based setup, because a page never downloads a catalogue 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 split the rest per locale. Measured against the usual alternatives, Intlayer reduces bundle and page size by up to 50%. See bundle optimization and the benchmark.
Largely. Follow the i18next migration guide to move the content over. You can also migrate gradually: the sync JSON plugin keeps your existing JSON catalogues as the source of truth and generates Intlayer dictionaries from them, so both layers stay in sync while you move components across one at a time.
Yes. The sync JSON plugin 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 does the same for gettext catalogues, and per locale files let you split content by language instead of grouping locales in one file.
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 catalogue one at a time. Step 11 of this guide walks through it.
For a fully automated pipeline, the Intlayer Compiler 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.
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 avoids both by keeping you in the loop.
Five pieces, all optional:
- VS Code extension: jump from a
useIntlayerkey 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: 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-intlanduse-intlcalls, which helps while you migrate. - MCP server: 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 fillitself. - Agent skills: focused skills such as
intlayer-config,intlayer-cliandintlayer-content, plus one per framework, that teach an agent your routing setup and the content node types. - ESLint plugin:
no-raw-textflags hardcoded strings, with further rules for static dictionary keys and unused content.
