localingos 0.1.14 → 0.1.15

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "localingos",
-  "version": "0.1.14",
+  "version": "0.1.15",
   "description": "CLI tool to sync translations with Localingos",
   "main": "src/index.js",
   "type": "module",

package/src/commands/extract.js

@@ -264,13 +264,6 @@ export function defineMessages<K extends string>(
 }
 \`\`\`
 
-- **Add a language/locale selector** to the app UI in the most appropriate, visible location (e.g., navigation bar, header, settings page, or footer). The selector must:
-  - Display the available locales based on the translation files present in \`${outputDir}/\`
-  - Allow users to switch languages at runtime
-  - Persist the user's language preference (e.g., localStorage)
-  - Use the project's i18n framework to change the active locale (e.g., \`i18n.changeLanguage(locale)\` for i18next)
-  - Show locale names in their native language when possible (e.g., "Español" not "Spanish", "Deutsch" not "German")
-  - If a locale selector component already exists in the project, update it rather than creating a duplicate`;
 ---
 
 ### Step 2: For EVERY component with translatable strings, create a co-located \`*${msgExt}\` file
@@ -429,7 +422,14 @@ ${messageDefinitionSection}${nonJsI18nInstructions}
 - If a string contains dynamic values like \`\${name}\` or \`{count}\`, use the i18n library's interpolation syntax: \`"Hello, {name}"\` in the source file, \`t('key', { name })\` in the code
 - Maintain the original text exactly as-is in the source file (in ${languageName})${isJsProject ? `
 - After creating all message files, run the extraction script to generate \`${sourceFile}\` from the message definitions` : ''}
-- After this is done, running \`localingos sync\` will push the source strings to Localingos and pull back translations for other languages — the app should already be wired to load those translated files from \`${outputDir}/\``;
+- After this is done, running \`localingos sync\` will push the source strings to Localingos and pull back translations for other languages — the app should already be wired to load those translated files from \`${outputDir}/\`
+- **Add a language/locale selector** to the app UI in the most appropriate, visible location (e.g., navigation bar, header, settings page, or footer). The selector must:
+  - Display the available locales based on the translation files present in \`${outputDir}/\`
+  - Allow users to switch languages at runtime
+  - Persist the user's language preference (e.g., localStorage)
+  - Use the project's i18n framework to change the active locale (e.g., \`i18n.changeLanguage(locale)\` for i18next)
+  - Show locale names in their native language when possible (e.g., "Español" not "Spanish", "Deutsch" not "German")
+  - If a locale selector component already exists in the project, update it rather than creating a duplicate`;
 
     // Print the prompt
     console.log(chalk.blue('🤖 AI Extraction Prompt'));