This is SDK for AutoLocalise.
A lightweight, efficient auto-translation SDK for React Native and Expo applications. This SDK provides seamless integration for automatic content translation with support for offline mode.
You don't need to prepare any translation files, just provide your API key and the SDK will handle the rest.
- π React Native and Expo support
- π Automatic string detection and translation
- π― Dynamic parameter interpolation
- π Static translation tracking
- π Offline mode support
- βοΈ Configurable cache TTL
- β‘οΈ Lightweight and efficient
npm install react-native-autolocalise @react-native-async-storage/async-storage
# or
yarn add react-native-autolocalise @react-native-async-storage/async-storageimport { TranslationProvider } from "react-native-autolocalise";
const App = () => {
const config = {
apiKey: "your-api-key",
sourceLocale: "fr",
targetLocale: "en",
// cacheTTL: 24, // Cache validity in hours (optional, defaults to 24)
};
return (
<TranslationProvider config={config}>
<YourApp />
</TranslationProvider>
);
};Basic usage:
import { useAutoTranslate } from "react-native-autolocalise";
const MyComponent = () => {
const { t, loading, error } = useAutoTranslate();
return (
<div>
<h1>{t("Welcome to our app!", "static")}</h1>
<p>{t("This text will be automatically translated")}</p>
</div>
);
};Use with params:
import { useAutoTranslate } from "react-native-autolocalise";
const MyComponent = () => {
const { t } = useAutoTranslate();
const name = "John";
return (
<div>
<p>
{t("Welcome, {{1}}!, Nice to meet you. {{2}}.")
.replace("{{1}}", name)
.replace("{{2}}", t("Have a great day!"))}
</p>
</div>
);
};The locale format follows the ISO 639-1 language code standard, optionally combined with an ISO 3166-1 country code:
- Language code only: 'en', 'fr', 'zh', 'ja', etc.
- Language-Region: 'en-US', 'fr-FR', 'zh-CN', 'pt-BR', etc.
In React Native, you can get the device locale using the Localization API:
import * as Localization from "react-native-localization";
// or
import { NativeModules, Platform } from "react-native";
// Using react-native-localization
const deviceLocale = Localization.locale; // e.g., 'en-US'
// Alternative method using native modules
const deviceLanguage =
Platform.OS === "ios"
? NativeModules.SettingsManager.settings.AppleLocale ||
NativeModules.SettingsManager.settings.AppleLanguages[0]
: NativeModules.I18nManager.localeIdentifier;In Expo, you can use the Localization API from expo-localization:
import * as Localization from "expo-localization";
// Get the device locale
const locale = Localization.locale; // e.g., 'en-US'
// Get just the language code
const languageCode = locale.split("-")[0]; // e.g., 'en'
// Get the user's preferred locales
const preferredLocales = Localization.locales; // e.g., ['en-US', 'en']
// Check if the device uses RTL layout
const isRTL = Localization.isRTL;Note: When running Expo in a web browser, it will use the browser's locale settings (navigator.language) automatically.
| Prop | Type | Description |
|---|---|---|
| config | TranslationConfig | Configuration object for the translation service |
| Property | Type | Required | Description |
|---|---|---|---|
| apiKey | string | Yes | Your API key for the translation service |
| sourceLocale | string | Yes | Source locale for translations |
| targetLocale | string | Yes | Target locale for translations |
| cacheTTL | number | No | Cache validity period in hours (default: 24) |
Tips: When sourceLocale === targetLocale no translation requests will be send.
Returns an object with:
t: Translation functionloading: Boolean indicating initialization of static translationserror: Error object if translation loading failed
When you pass the 'static' parameter to the translation function, the translation will be persisted so that you can review and edit in the dashboard, default is non-static, nothing will be persisted.
import { useAutoTranslate } from "react-native-autolocalise";
const MyComponent = () => {
const { t } = useAutoTranslate();
return (
<div>
<h1>{t("Welcome to our app!", "static")}</h1>
</div>
);
};Contributions are welcome! Please feel free to submit a Pull Request.
MIT