i18n

Synchronize i18next configuration between Madoc TS server and client.

57|15|Updated Nov 28, 2018
One-click install
npx skills add https://github.com/digirati-co-uk/madoc-platform --skill i18n-digirati-co-uk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: i18n
Source: https://github.com/digirati-co-uk/madoc-platform/tree/main/.agents/skills/i18n
Command: npx skills add https://github.com/digirati-co-uk/madoc-platform --skill i18n-digirati-co-uk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It ensures consistent internationalization configuration across Madoc TS server and client, preventing mismatched namespaces and broken locale loading.

Core Features & Use Cases

  • Unified i18next setup: Keeps server‑side and client‑side detection and backend configuration in sync.
  • Locale path management: Aligns loading paths and endpoint routes for multilingual content.
  • Namespace coordination: Guarantees that added translation namespaces are reflected on both sides.

Quick Start

Use the i18n skill to review and update the i18next server and client configuration for a new language.

Frequently Asked Questions about i18n

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I align i18next configuration between a TypeScript server and client?

To align i18next configuration across a TypeScript server and client, you must synchronize detection order, backend settings, and locale loading paths to prevent mismatched namespaces and ensure consistent multilingual content delivery.

Why are my translation namespaces mismatched between the Madoc TS server and client?

Translation namespaces mismatch between the Madoc TS server and client when i18next configurations are not synchronized, requiring you to update detection order and backend settings to coordinate namespace handling on both sides.

What is the best way to synchronize multilingual locale loading paths in Madoc TS?

The best way to synchronize multilingual locale loading paths in Madoc TS is to align the i18next backend settings and endpoint routes, ensuring the server and client fetch translation namespaces from the correct locations.

Can I use this skill to update detection order for new languages in i18next?

Yes, you can use this skill to review and update the i18next server and client configuration for a new language, specifically modifying the detection order and backend settings to support multilingual functionality.

Does updating i18next locale endpoints require changes to both Koa server and client settings?

Updating i18next locale endpoints requires changes to both the Koa server and client settings to guarantee correct locale endpoint responses and ensure consistent namespace handling across the Madoc TS services.

When do I need to update i18next settings for Madoc TS services?

You need to update i18next settings for Madoc TS services when adding a new language or modifying multilingual configurations, ensuring unified detection order and backend setup to prevent broken locale loading.