The content of this page was translated using an AI.
See the last version of the original content in EnglishGetting Started Internationalising (i18n) with Intlayer and Vite and React
What is Intlayer?
Intlayer is an innovative, open-source internationalisation (i18n) library designed to simplify multilingual support in modern web applications.
With Intlayer, you can:
- Easily manage translations using declarative dictionaries at the component level.
- Dynamically localise metadata, routes, and content.
- Ensure TypeScript support with autogenerated types, improving autocompletion and error detection.
- Benefit from advanced features, like dynamic locale detection and switching.
Step-by-Step Guide to Set Up Intlayer in a Vite and React Application
Step 1: Install Dependencies
Install the necessary packages using npm:
npm install intlayer react-intlayer vite-intlayer
intlayer
The core package that provides internationalisation tools for configuration management, translation, content declaration, transpilation, and CLI commands.
react-intlayer The package that integrates Intlayer with React application. It provides context providers and hooks for React 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.
Step 2: Configuration of your project
Create a config file to configure the languages of your application:
import { Locales, type IntlayerConfig } from "intlayer";const config: IntlayerConfig = { internationalisation: { 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.
Step 3: Integrate Intlayer in Your Vite Configuration
Add the intlayer plugin into your configuration.
import { defineConfig } from "vite";import react from "@vitejs/plugin-react-swc";import { intlayerPlugin } from "vite-intlayer";// https://vitejs.dev/config/export default defineConfig({ plugins: [react(), intlayerPlugin()],});
The intlayerPlugin() 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.
Step 4: Declare Your Content
Create and manage your content declarations to store translations:
import { t, type Dictionary } from "intlayer";import type { ReactNode } from "react";const appContent = { key: "app", content: { viteLogo: t({ en: "Vite logo", "en-GB": "Vite logo", fr: "Logo Vite", es: "Logo Vite", }), reactLogo: t({ en: "React logo", "en-GB": "React logo", fr: "Logo React", es: "Logo React", }), title: "Vite + React", count: t({ en: "count is ", "en-GB": "count is ", fr: "le compte est ", es: "el recuento es ", }), edit: t<ReactNode>({ en: ( <> Edit <code>src/App.tsx</code> and save to test HMR </> ), "en-GB": ( <> Edit <code>src/App.tsx</code> and save to test HMR </> ), fr: ( <> Éditez <code>src/App.tsx</code> et enregistrez pour tester HMR </> ), es: ( <> Edita <code>src/App.tsx</code> y guarda para probar HMR </> ), }), readTheDocs: t({ en: "Click on the Vite and React logos to learn more", "en-GB": "Click on the Vite and React logos to learn more", fr: "Cliquez sur les logos Vite et React pour en savoir plus", es: "Haga clic en los logotipos de Vite y React para obtener más información", }), },} satisfies Dictionary;export default appContent;
Your content declarations can be defined anywhere in your application as soon they are included into the contentDir directory (by default, ./src). And match the content declaration file extension (by default, .content.{json,ts,tsx,js,jsx,mjs,mjx,cjs,cjx}). For more details, refer to the content declaration documentation. If your content file includes TSX code, you should consider importing import React from "react"; in your content file.
Step 5: Utilise Intlayer in Your Code
Access your content dictionaries throughout your application:
import { useState, type FC } from "react";import reactLogo from "./assets/react.svg";import viteLogo from "/vite.svg";import "./App.css";import { IntlayerProvider, useIntlayer } from "react-intlayer";const AppContent: FC = () => { const [count, setCount] = useState(0); const content = useIntlayer("app"); return ( <> <div> <a href="https://vitejs.dev" target="_blank"> <img src={viteLogo} className="logo" alt={content.viteLogo.value} /> </a> <a href="https://react.dev" target="_blank"> <img src={reactLogo} className="logo react" alt={content.reactLogo.value} /> </a> </div> <h1>{content.title}</h1> <div className="card"> <button onClick={() => setCount((count) => count + 1)}> {content.count} {count} </button> <p>{content.edit}</p> </div> <p className="read-the-docs">{content.readTheDocs}</p> </> );};const App: FC = () => ( <IntlayerProvider> <AppContent /> </IntlayerProvider>);export default App;
If you want to use your content in a string attribute, such as alt, title, href, aria-label, etc., you must call the value of the function, like:
jsx<img src={content.image.src.value} alt={content.image.value} />
To Learn more about the useIntlayer hook, refer to the documentation.
(Optional) Step 6: Change the language of your content
To change the language of your content, you can use the setLocale function provided by the useLocale hook. This function allows you to set the locale of the application and update the content accordingly.
import type { FC } from "react";import { Locales } from "intlayer";import { useLocale } from "react-intlayer";const LocaleSwitcher: FC = () => { const { setLocale } = useLocale(); return ( <button onClick={() => setLocale(Locales.English)}> Change Language to English </button> );};
To Learn more about the useLocale hook, refer to the documentation.
(Optional) Step 7: Add Localised Routing to your Application
The purpose of this step is to make unique routes for each language. This is useful for SEO and SEO-friendly URLs. Example:
- https://example.com/about- https://example.com/es/about- https://example.com/fr/about
By default, the routes are not prefixed for the default locale. If you want to prefix the default locale, you can set the middleware.prefixDefault option to true in your configuration. See the configuration documentation for more information.
To add localised routing to your application, you can create a LocaleRouter component that wraps your application's routes and handles locale-based routing. Here is an example using React Router:
// Importing necessary dependencies and functionsimport { type Locales, configuration, getPathWithoutLocale } from "intlayer"; // Utility functions and types from 'intlayer'import type { FC, PropsWithChildren } from "react"; // React types for functional components and propsimport { IntlayerProvider } from "react-intlayer"; // Provider for internationalisation contextimport { BrowserRouter, Routes, Route, Navigate, useLocation,} from "react-router-dom"; // Router components for managing navigation// Destructuring configuration from Intlayerconst { internationalisation, middleware } = getConfiguration();const { locales, defaultLocale } = internationalisation;/** * A component that handles localisation and wraps children with the appropriate locale context. * It manages URL-based locale detection and validation. */const AppLocalised: FC<PropsWithChildren<{ locale: Locales }>> = ({ children, locale,}) => { const { pathname, search } = useLocation(); // Get the current URL path // Determine the current locale, falling back to the default if not provided const currentLocale = locale ?? defaultLocale; // Remove the locale prefix from the path to construct a base path const pathWithoutLocale = getPathWithoutLocale( pathname // Current URL path ); /** * If middleware.prefixDefault is true, the default locale should always be prefixed. */ if (middleware.prefixDefault) { // Validate the locale if (!locale || !locales.includes(locale)) { // Redirect to the default locale with the updated path return ( <Navigate to={`/${defaultLocale}/${pathWithoutLocale}${search}`} replace // Replace the current history entry with the new one /> ); } // Wrap children with the IntlayerProvider and set the current locale return ( <IntlayerProvider locale={currentLocale}>{children}</IntlayerProvider> ); } else { /** * When middleware.prefixDefault is false, the default locale is not prefixed. * Ensure that the current locale is valid and not the default locale. */ if ( currentLocale.toString() !== defaultLocale.toString() && !locales .filter( (locale) => locale.toString() !== defaultLocale.toString() // Exclude the default locale ) .includes(currentLocale) // Check if the current locale is in the list of valid locales ) { // Redirect to the path without locale prefix return <Navigate to={`${pathWithoutLocale}${search}`} replace />; } // Wrap children with the IntlayerProvider and set the current locale return ( <IntlayerProvider locale={currentLocale}>{children}</IntlayerProvider> ); }};/** * A router component that sets up locale-specific routes. * It uses React Router to manage navigation and render localised components. */export const LocaleRouter: FC<PropsWithChildren> = ({ children }) => ( <BrowserRouter> <Routes> {locales .filter( (locale) => middleware.prefixDefault || locale !== defaultLocale ) .map((locale) => ( <Route // Route pattern to capture the locale (e.g., /en/, /fr/) and match all subsequent paths path={`/${locale}/*`} key={locale} element={<AppLocalised locale={locale}>{children}</AppLocalised>} // Wraps children with locale management /> ))} { // If prefixing the default locale is disabled, render the children directly at the root path !middleware.prefixDefault && ( <Route path="*" element={ <AppLocalised locale={defaultLocale}>{children}</AppLocalised> } // Wraps children with locale management /> ) } </Routes> </BrowserRouter>);
Then, you can use the LocaleRouter component in your application:
import { LocaleRouter } from "./components/LocaleRouter";import type { FC } from "react";// ... Your AppContent componentconst App: FC = () => ( <LocaleRouter> <AppContent /> </LocaleRouter>);
In parallel, you can also use the intLayerMiddlewarePlugin to 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.
import { defineConfig } from "vite";import react from "@vitejs/plugin-react-swc";import { intlayerPlugin, intLayerMiddlewarePlugin } from "vite-intlayer";// https://vitejs.dev/config/export default defineConfig({ plugins: [react(), intlayerPlugin(), intLayerMiddlewarePlugin()],});
(Optional) Step 8: Change the URL when the locale changes
To change the URL when the locale changes, you can use the onLocaleChange prop provided by the useLocale hook. In parallel, you can use the useLocation and useNavigate hooks from react-router-dom to update the URL path.
import { useLocation, useNavigate } from "react-router-dom";import { Locales, getHTMLTextDir, getLocaleName, getLocalizedUrl,} from "intlayer";import { useLocale } from "react-intlayer";import { type FC } from "react";const LocaleSwitcher: FC = () => { const { pathname, search } = useLocation(); // Get the current URL path. Example: /en-GB/about?foo=bar const navigate = useNavigate(); const { locale, availableLocales, setLocale } = useLocale({ * Custom hook to update the HTML `lang` and `dir` attributes based on the current locale. */const useI18nHTMLAttributes = () => { const { locale } = useLocale(); useEffect(() => { const htmlElement = document.documentElement; // Update the `lang` attribute to match the current locale htmlElement.lang = locale; // Update the `dir` attribute to match the text direction of the current locale htmlElement.dir = getHTMLTextDir(locale); }, [locale]);};export default useI18nHTMLAttributes;
Using the Hook
Call the useI18nHTMLAttributes hook in your application's root component to ensure the attributes are updated whenever the locale changes:
import React from "react";import { LocaleProvider } from "react-intlayer";import useI18nHTMLAttributes from "./hooks/useI18nHTMLAttributes";const App = () => { useI18nHTMLAttributes(); return <LocaleProvider>{/* Your application components */}</LocaleProvider>;};export default App;
By implementing this hook, your application will dynamically adjust the lang and dir attributes of the <html> tag, ensuring a seamless and accessible experience for users across different locales.
Documentation References
- useLocale hook
- getHTMLTextDir hook
- lang attribute
- Updates the HTML element's lang and dir attributes based on the current locale.
- lang: Informs browsers and search engines of the page's language.
- dir: Ensures the correct reading order (e.g., 'ltr' for English, 'rtl' for Arabic). *
- This dynamic update is essential for proper text rendering, accessibility, and SEO. */ export const useI18nHTMLAttributes = () => { const { locale } = useLocale();
useEffect(() => { // Update the language attribute to the current locale. document.documentElement.lang = locale;
// Set the text direction based on the current locale. document.documentElement.dir = getHTMLTextDir(locale);}, [locale]); };
```jsx fileName="src/hooks/useI18nHTMLAttributes.msx" codeFormat="esm" import { useEffect } from "react"; import { useLocale } from "react-intlayer"; import { getHTMLTextDir } from "intlayer"; /** * Updates the HTML <html> element's `lang` and `dir` attributes based on the current locale. * - `lang`: Informs browsers and search engines of the page's language. * - `dir`: Ensures the correct reading order (e.g., 'ltr' for English, 'rtl' for Arabic). * * This dynamic update is essential for proper text rendering, accessibility, and SEO. */ export const useI18nHTMLAttributes = () => { const { locale } = useLocale(); useEffect(() => { // Update the language attribute to the current locale. document.documentElement.lang = locale; // Set the text direction based on the current locale. document.documentElement.dir = getHTMLTextDir(locale); }, [locale]); };Using the Hook in Your Application
Integrate the hook into your main component so that the HTML attributes update whenever the locale changes:
import type { FC } from "react";import { IntlayerProvider, useIntlayer } from "react-intlayer";import { useI18nHTMLAttributes } from "./hooks/useI18nHTMLAttributes";import "./App.css";const AppContent: FC = () => { // Apply the hook to update the <html> tag's lang and dir attributes based on the locale. useI18nHTMLAttributes(); // ... Rest of your component};const App: FC = () => ( <IntlayerProvider> <AppContent /> </IntlayerProvider>);export default App;
By applying these changes, your application will:
- Ensure the language (lang) attribute correctly reflects the current locale, which is important for SEO and browser behaviour.
- Adjust the text direction (dir) according to the locale, enhancing readability and usability for languages with different reading orders.
- Provide a more accessible experience, as assistive technologies depend on these attributes to function optimally.
(Optional) Step 10: Creating a Localised Link Component
To ensure that your application’s navigation respects the current locale, you can create a custom Link component. This component automatically prefixes internal URLs with the current language, so that. For example, when a French-speaking user clicks on a link to the "About" page, they are redirected to /fr/about instead of /about.
This behaviour is useful for several reasons:
- SEO and User Experience: Localised URLs help search engines index language-specific pages correctly and provide users with content in their preferred language.
- Consistency: By using a localised link throughout your application, you guarantee that navigation stays within the current locale, preventing unexpected language switches.
- Maintainability: Centralising the localisation logic in a single component simplifies the management of URLs, making your codebase easier to maintain and extend as your application grows.
Below is the implementation of a localised Link component in TypeScript:
import { getLocalizedUrl } from "intlayer";import { forwardRef, type DetailedHTMLProps, type AnchorHTMLAttributes,} from "react";import { useLocale } from "react-intlayer";export interface LinkProps extends DetailedHTMLProps< AnchorHTMLAttributes<HTMLAnchorElement>, HTMLAnchorElement > {}/** * Utility function to check whether a given URL is external. * If the URL starts with http:// or https://, it's considered external. */export const checkIsExternalLink = (href?: string): boolean => /^https?:///.test(href ?? "");/** * A custom Link component that adapts the href attribute based on the current locale. * For internal links, it uses `getLocalizedUrl` to prefix the URL with the locale (e.g., /fr/about). * This ensures that navigation stays within the same locale context. */export const Link = forwardRef<HTMLAnchorElement, LinkProps>( ({ href, children, ...props }, ref) => { const { locale } = useLocale(); const isExternalLink = checkIsExternalLink(href); // If the link is internal and a valid href is provided, get the localised URL. const hrefI18n = href && !isExternalLink ? getLocalizedUrl(href, locale) : href; return ( <a href={hrefI18n} ref={ref} {...props}> {children} </a> ); });Link.displayName = "Link";
How It Works
Detecting External Links:
The helper function checkIsExternalLink determines whether a URL is external. External links are left unchanged because they do not need localisation.Retrieving the Current Locale:
The useLocale hook provides the current locale (e.g., fr for French).Localising the URL:
For internal links (i.e., non-external), getLocalizedUrl is used to automatically prefix the URL with the current locale. This means that if your user is in French, passing /about as the href will transform it to /fr/about.Returning the Link:
The component returns an <a> element with the localised URL, ensuring that navigation is consistent with the locale.
By integrating this Link component across your application, you maintain a coherent and language-aware user experience while also benefiting from improved SEO and usability.
Configure TypeScript
Intlayer uses module augmentation to get the benefits of TypeScript and make your codebase stronger.
Ensure your TypeScript configuration includes the autogenerated types.
{ // ... Your existing TypeScript configurations "include": [ // ... Your existing TypeScript configurations ".intlayer/**/*.ts", // Include the autogenerated types ],}
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:
# Ignore the files generated by Intlayer.intlayer
Go Further
To go further, you can implement the visual editor or externalise your content using the CMS.
If you have an idea for improving this documentation, please feel free to contribute by submitting a pull request on GitHub.
GitHub link to the documentation