# General Translation Changelog: gt-react 10.8.0: Feature-flagged i18n
URL: https://generaltranslation.com/en-GB/blog/gt-react_v10_8_0.mdx
Docs index: https://generaltranslation.com/llms.txt
Description: 
Authors: Ernest McCarter
Published: 2025-11-14

## Overview

In **gt-react 10.8.0**, we've added feature flag support through the `enableI18n` field. This lets you conditionally disable internationalisation, with support for both synchronous and asynchronous loading patterns.

***

## Synchronous Behaviour

When `enableI18n` is set to `false`, i18n functionality is disabled by:

* setting the locale list to only the default locale
* setting the user's locale to the default locale

```tsx
<GTProvider enableI18n={false}>
  {/* i18n disabled - only default locale available */}
</GTProvider>
```

***


## Asynchronous Behaviour

For dynamic feature flags, use `enableI18nLoaded` to indicate the loading state:

```tsx
<GTProvider 
  enableI18n={featureFlag} 
  enableI18nLoaded={isLoaded}
>
  {/* Content */}
</GTProvider>
```

When `enableI18nLoaded` is not `undefined`:

* `false`: The feature flag is loading (uses the default `enableI18n` value)
* `true`: The feature flag has finished loading

While loading, the library checks the `generaltranslation.enable-i18n` cookie to determine the current state. Once loaded, the explicit `enableI18n` value takes precedence.

***


## SSG/SSR Considerations

With SSG, the first render cycle is effectively sacrificed when the default `enableI18n` value is `false`, as static generation cannot determine the runtime feature flag state.

SSR currently behaves in a similar way, though we plan to add proper SSR support for Next.js Pages Router in future releases. For Next.js App Router, use `gt-next` instead.

## Sitemap

See the full [sitemap](https://generaltranslation.com/sitemap.md) for all pages.