src/frontend/i18next-parser.config.json

{
  "defaultNamespace": "global",
  "input": ["src/**/*.{ts,tsx}", "!src/styled-system/**/*", "!src/**/*.d.ts"],
  "output": "src/locales/$LOCALE/$NAMESPACE.json",
  "createOldCatalogs": false,
  "locales": ["en", "fr", "de", "nl"],
  "sort": true
}
🌐(frontend) init i18next - dynamically load locale files for smaller footprint - have a namespace for each feature. At first I'd figured I'd put each namespace in its correct feature folder but it's kinda cumbersome to manage if we want to link that to i18n management services like crowdin… 2024-07-18 13:59:50 +02:00			`{`
			`"defaultNamespace": "global",`
			`"input": ["src/*/.{ts,tsx}", "!src/styled-system/*/", "!src/*/.d.ts"],`
			`"output": "src/locales/$LOCALE/$NAMESPACE.json",`
			`"createOldCatalogs": false,`
🌐(frontend) add Dutch translation Add Dutch to the language selection system, and add configuration files with Dutch translated messages. 2025-03-04 10:14:13 +01:00			`"locales": ["en", "fr", "de", "nl"],`
🌐(frontend) sort extrated locales to help prevent conflicts when adding keys by hand, we didn't really know where to add them so that the i18n:extract command would not move them afterwards. Feels like this will help. I guess a CI thing checking if the locales file dont change after a push would be helpful 2024-07-21 17:23:42 +02:00			`"sort": true`
🌐(frontend) init i18next - dynamically load locale files for smaller footprint - have a namespace for each feature. At first I'd figured I'd put each namespace in its correct feature folder but it's kinda cumbersome to manage if we want to link that to i18n management services like crowdin… 2024-07-18 13:59:50 +02:00			`}`