Skip to main content

Setup with Vite

The Lingui Vite integration:

Setup with @vitejs/plugin-react​

@vitejs/plugin-react uses Babel to transform your code. LinguiJS relies on @lingui/babel-plugin-lingui-macro to compile JSX to ICU Message Format and for automatic ID generation.

  1. Install @lingui/cli, @lingui/vite-plugin, @lingui/babel-plugin-lingui-macro as development dependencies and @lingui/react as a runtime dependency:

    npm install --save-dev @lingui/cli @lingui/vite-plugin @lingui/babel-plugin-lingui-macro
    npm install --save @lingui/react

  2. Setup Lingui in vite.config.ts:

    info

    @vitejs/plugin-react does not use babel config (e.g. babel.rc) from your project by default. You have to enable it manually or specify babel options directly in vite.config.ts

    vite.config.ts
    import { defineConfig } from "vite";
    import react from "@vitejs/plugin-react";
    import { lingui } from "@lingui/vite-plugin";

    export default defineConfig({
      plugins: [
        react({
          babel: {
            plugins: ["@lingui/babel-plugin-lingui-macro"],
          },
        }),
        lingui(),
      ],
    });

Setup with @vitejs/plugin-react-swc​

@vitejs/plugin-react-swc uses SWC to transform your code, which is 20x faster than Babel. LinguiJS relies on @lingui/swc-plugin to compile JSX to ICU Message Format and for automatic ID generation.

  1. Install @lingui/cli, @lingui/swc-plugin as development dependencies and @lingui/react as a runtime dependency:

    npm install --save-dev @lingui/cli @lingui/vite-plugin @lingui/swc-plugin
    npm install --save @lingui/react
    note

    SWC Plugin support is still experimental. Semver backwards compatibility between different @swc/core versions is not guaranteed.

    You need to select an appropriate version of the @lingui/swc-plugin to match compatible @swc/core version.

    The version of @swc/core is specified within the @vitejs/plugin-react-swc package.

    To ensure that the resolved version of @swc/core is one of the supported versions, you may utilize the resolutions field in the package.json file, which is supported by Yarn:

    "resolutions": {
      "@swc/core": "1.3.56"
    },

    or overrides for >npm@8.3

    "overrides": {
      "@swc/core": "1.3.56"
    },

    For more information about compatibility, see the plugins.swc.rs page.

  2. Setup Lingui in vite.config.ts:

    vite.config.ts
    import { defineConfig } from "vite";
    import react from "@vitejs/plugin-react-swc";
    import { lingui } from "@lingui/vite-plugin";

    export default defineConfig({
      plugins: [
        react({
          plugins: [["@lingui/swc-plugin", {}]],
        }),
        lingui(),
      ],
    });

Further Setup​

  1. Create a lingui.config.ts file with LinguiJS configuration in the root of your project (next to package.json). Replace src with the directory name where you have source files:

    lingui.config.ts
    import type { LinguiConfig } from "@lingui/conf";

    const config: LinguiConfig = {
      locales: ["en", "cs", "fr"],
      catalogs: [
        {
          path: "<rootDir>/src/locales/{locale}",
          include: ["src"],
        },
      ],
    };

    export default config;

    The PO format is recommended for message catalogs, and could be compiled on the fly thanks to @lingui/vite-plugin. See Catalog Formats for other available formats.

  2. Add the following scripts to your package.json:

    package.json
    {
      "scripts": {
        "messages:extract": "lingui extract"
      }
    }

  3. Check the installation by running:

    npm run messages:extract

    There should be no error and you should see output similar following:

    > npm run messages:extract

    Catalog statistics:
    ┌──────────┬─────────────┬─────────┐
    │ Language │ Total count │ Missing │
    ├──────────┼─────────────┼─────────┤
    │ cs       │     0       │   0     │
    │ en       │     0       │   0     │
    │ fr       │     0       │   0     │
    └──────────┴─────────────┴─────────┘

    (use "lingui extract" to update catalogs with new messages)
    (use "lingui compile" to compile catalogs for production)

    This command should create .po catalogs in the src/locales/ folder:

    src
    └── locales
       ├── cs.po
       ├── en.po
       └── fr.po

  4. Import .po those files directly in your Vite processed code:

    export async function dynamicActivate(locale: string) {
      const { messages } = await import(`./locales/${locale}.po`);

      i18n.load(locale, messages);
      i18n.activate(locale);
    }

See the Dynamic loading of message catalogs for more info.

tip

Don't miss the Lingui ESLint Plugin which can help you find and prevent common l10n mistakes in your code.

See Also​