Namespaces

In the Getting Started section, we implemented a basic i18n automatic lazy loading feature. However, as the project grows, resource files may become large, and we need fine-grained control over them.

vite-plugin-i18n-ally provides the namespace configuration to enable namespaces. When enabled, the plugin generates corresponding resource files based on namespaces to reduce file size.

You can set i18n-ally.namespace:

{
  "i18n-ally.namespace": true,
  "i18n-ally.pathMatcher": "{locale}/{namespace}.{ext}"
}

or configure it in vite.config.ts:

import { defineConfig } from 'vite'
import { i18nAlly } from 'vite-plugin-i18n-ally'

export default defineConfig({
  plugins: [
    i18nAlly({
      namespace: true,
      pathMatcher: '{locale}/{namespace}.{ext}',
    }),
  ],
})

After enabling namespaces, resource files will be generated based on namespaces. However, how to load these resource files is a client-side concern.

There are two ways to load resource files:

1. Load all resource files at once
2. Load resource files based on routes

Load all resource files at once

We can add the corresponding namespace resource files to the internationalization library in the onResourceLoaded hook:

import { I18nAllyClient } from 'vite-plugin-i18n-ally/client'

new I18nAllyClient({
  onResourceLoaded: (resources) => {
    i18next.addResourceBundle(lng, ns, resources)
  },
})

This method is simple and straightforward, but the browser will load all resource files for the current language. Splitting namespaces doesn't make much sense.

Load resource files based on routes

Since it involves routes, we naturally think of react-router. In react-router^6.4, loader was added to load resource files in the loader.

import { createRoutesFromElements, Route } from 'react-router'
import { I18nAllyClient } from 'vite-plugin-i18n-ally/client'

const i18nAlly = I18nAllyClient(
  /// ...
)

const routes = createRoutesFromElements(
  <Route path='/'>
    <Route
      path='a'
      lazy={() => import('./a')}
      loader={async () => {
        await i18nAlly.asyncLoadResource(i18next.language, {
          ns: ['a']
        })
      }}
    />
  </Route>
)

This way, we can load the corresponding resource files based on the route, achieving on-demand loading of resource files.

For more advanced methods, you can use vite-plugin-remix-flat-routes or remix.

References:

• Implementation with vite-plugin-remix-flat-routes
• Implementation with remix