القائمة
Guide for combining Better Translate packages without duplicating translation ownership.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Extract source strings, generate locale files, and remove unused keys for Better Translate projects.
Expo and React Native integration guide using Better Translate React support.
React and Expo integration guide for Better Translate providers, hooks, and typed translation access.
Package map and reading order for Better Translate product skills.
Smallest Better Translate setup for plain TypeScript, Node.js, Bun, APIs, and shared libraries.
Map of Better Translate example apps to copy from when starting a new integration.
| name | combined |
| description | Guide for combining Better Translate packages without duplicating translation ownership. |
Use this guide when the app needs more than one Better Translate package.
@better-translate/core@better-translate/react@better-translate/core@better-translate/nextjs@better-translate/core@better-translate/nextjs@better-translate/react@better-translate/core@better-translate/tanstack-router@better-translate/react@better-translate/core@better-translate/astro@better-translate/mdAdd @better-translate/cli to any combination above when you want the CLI to manage locale file creation.
Example - Next.js app with generated translations:
@better-translate/core@better-translate/nextjs@better-translate/cliEvery combination still works best when one shared exported translator stays the source of truth. Let adapters, hooks, and helpers read from that same typed translator instead of recreating locale rules in multiple places.
Every combination still has one source of truth:
Do not duplicate locale rules in multiple places.