@lang-tag/cli 0.16.0 → 0.18.0

package/README.md

@@ -1,6 +1,5 @@
 # Lang-tag CLI
 
-
 A professional solution for managing translations in modern JavaScript/TypeScript projects, especially those using component-based architectures. `lang-tag` simplifies internationalization by allowing you to define translation keys directly within the components where they are used. Translations become local, callable function objects with full TypeScript support, IntelliSense, and compile-time safety.
 
 ## Key Benefits
@@ -15,7 +14,7 @@ The core is optimized for performance, with a bundle size of just **~1KB** ([che
 
 ### Effortless translation structure
 
-Instead of manually managing centralized translation files, `lang-tag` lets you colocate keys within components and automatically organizes them into namespaces based on your project structure. For example, all components in `components/orders` or pages in `pages/order` share the `orders` namespace. You define a simple directory-to-namespace mapping once, and `lang-tag` handles merging and file organization—while you retain full control over how namespaces are merged. 
+Instead of manually managing centralized translation files, `lang-tag` lets you colocate keys within components and automatically organizes them into namespaces based on your project structure. For example, all components in `components/orders` or pages in `pages/order` share the `orders` namespace. You define a simple directory-to-namespace mapping once, and `lang-tag` handles merging and file organization—while you retain full control over how namespaces are merged.
 
 > Set your rules, then let `lang-tag` do the rest.
 
@@ -31,6 +30,7 @@ Full functionality is available through an advanced CLI that keeps your applicat
 ### Practical and Flexible Architecture
 
 The solution provides:
+
 - **Framework agnostic** – works with any JavaScript/TypeScript project and integrates easily with libraries like react-i18next
 - **Library ecosystem support** - create reusable component libraries with embedded lang-tag translations that consuming lang-tag applications can easily import/integrate and override
 - **Full TypeScript support** - complete type safety with IntelliSense for all translation keys and interpolation parameters
@@ -49,21 +49,24 @@ Instead of maintaining separate translation files and complex key mappings, tran
 // Component with colocated translations using custom i18n tag
 import { i18n } from '../utils/i18n';
 
-const translations = i18n({
-    greeting: 'Welcome {{name}} to our store!',
-    orderSummary: 'You have {{count}} items in your cart.',
-    actions: {
-        proceed: 'Proceed to Payment',
-        cancel: 'Cancel Order'
+const translations = i18n(
+    {
+        greeting: 'Welcome {{name}} to our store!',
+        orderSummary: 'You have {{count}} items in your cart.',
+        actions: {
+            proceed: 'Proceed to Payment',
+            cancel: 'Cancel Order',
+        },
+    },
+    {
+        namespace: 'orders',
+        path: 'components.checkout',
     }
-}, {
-    namespace: 'orders',
-    path: 'components.checkout'
-});
+);
 
 function CheckoutComponent({ name, count }) {
     const t = translations.useT();
-    
+
     return (
         <div>
             <h2>{t.greeting({ name })}</h2>
@@ -82,16 +85,19 @@ function CheckoutComponent({ name, count }) {
 The `lang-tag` ecosystem provides tooling to transform colocated definitions into production-ready translation files:
 
 **Collection & Organization**
+
 - The `lang-tag collect` command discovers translation tags throughout your codebase
 - Translations are organized into namespace-based JSON files (e.g., `public/locales/en/orders.json`)
 - Hierarchical key structures can be automatically generated based on configuration rules (eg.: based on component paths)
 
 **Dynamic Configuration Management**
+
 - Configuration parameters can be automatically generated using `onConfigGeneration` rules
 - Namespace and path assignments can be derived from custom logic (eg.: by file structure, component location)
 - The `lang-tag regenerate-tags` command updates source code configurations dynamically
 
 **Development-Time Optimization**
+
 - Watch mode (`lang-tag watch`) provides real-time translation collection during development
 - Changes to translation definitions trigger automatic regeneration of translation files
 - Full TypeScript integration ensures compile-time validation of translation keys and parameters
@@ -99,16 +105,19 @@ The `lang-tag` ecosystem provides tooling to transform colocated definitions int
 ### Enterprise Integration Capabilities
 
 **Framework Agnostic Architecture**
+
 - Core library provides building blocks (like `createCallableTranslations`) for creating custom tag functions
 - Seamless integration with existing i18n libraries (i18next, react-i18next, etc.)
 - Maintains compatibility with current translation workflows while enhancing developer experience
 
 **Library Ecosystem Support**
+
 - Component libraries can embed translations using `.lang-tag.exports.json` manifests
 - The `lang-tag import` command automatically discovers and integrates library translations
 - Consuming applications maintain full control over translation overrides and customization
 
 **Type-Safe Translation Experience**
+
 - Complete TypeScript support with IntelliSense for all translation keys
 - Compile-time validation of interpolation parameters
 - Callable translation objects provide intuitive API with full type inference
@@ -134,4 +143,4 @@ For detailed setup, usage, and advanced features, please refer to the documentat
 - [React-i18next Example](docs/react-i18n-example.md)
 - [Library Support](docs/library-support.md)
 - [API Reference](docs/api-reference.md)
-- [Flexible Translation Definitions](docs/flexible-translations.md)
+- [Flexible Translation Definitions](docs/flexible-translations.md)

package/algorithms/collector/dictionary-collector.d.ts

@@ -1,5 +1,5 @@
-import { TranslationsCollector } from './type.ts';
-import { LangTagCLIProcessedTag } from '../../config.ts';
+import { TranslationsCollector } from './type';
+import { LangTagCLIProcessedTag } from '../../type';
 interface Options {
     appendNamespaceToPath: boolean;
 }

package/algorithms/collector/index.d.ts

@@ -5,6 +5,6 @@
  * during the collection process. Each collector implements a different strategy
  * for organizing translations (e.g., single dictionary vs. namespace-based files).
  */
-export { DictionaryCollector } from './dictionary-collector.ts';
-export { NamespaceCollector } from './namespace-collector.ts';
-export { type TranslationsCollector } from './type.ts';
+export { DictionaryCollector } from './dictionary-collector';
+export { NamespaceCollector } from './namespace-collector';
+export { type TranslationsCollector } from './type';

package/algorithms/collector/namespace-collector.d.ts

@@ -1,5 +1,5 @@
-import { TranslationsCollector } from './type.ts';
-import { LangTagCLIProcessedTag } from '../../config.ts';
+import { TranslationsCollector } from './type';
+import { LangTagCLIProcessedTag } from '../../type';
 export declare class NamespaceCollector extends TranslationsCollector {
     private clean;
     private languageDirectory;

package/algorithms/collector/type.d.ts

@@ -1,5 +1,5 @@
-import { LangTagCLIConfig, LangTagCLIProcessedTag } from '../../config.ts';
-import { LangTagCLILogger } from '../../logger.ts';
+import { LangTagCLILogger } from '../../logger';
+import { LangTagCLIConfig, LangTagCLIProcessedTag } from '../../type';
 export declare abstract class TranslationsCollector {
     config: LangTagCLIConfig;
     logger: LangTagCLILogger;

package/algorithms/config-generation/config-keeper.d.ts

@@ -1,4 +1,4 @@
-import { LangTagCLIConfigGenerationEvent } from '../../config.ts';
+import { LangTagCLIConfigGenerationEvent } from '../../type';
 export type ConfigKeeperMode = 'namespace' | 'path' | 'both';
 export interface ConfigKeeperOptions {
     /**

package/algorithms/config-generation/index.d.ts

@@ -4,6 +4,6 @@
  * These algorithms customize how translation tag configurations are generated
  * during collection and regeneration.
  */
-export { pathBasedConfigGenerator, type PathBasedConfigGeneratorOptions } from './path-based-config-generator.ts';
-export { configKeeper, type ConfigKeeperOptions, type ConfigKeeperMode } from './config-keeper.ts';
-export { prependNamespaceToPath, type PrependNamespaceToPathOptions } from './prepend-namespace-to-path.ts';
+export { pathBasedConfigGenerator, type PathBasedConfigGeneratorOptions, } from './path-based-config-generator';
+export { configKeeper, type ConfigKeeperOptions, type ConfigKeeperMode, } from './config-keeper';
+export { prependNamespaceToPath, type PrependNamespaceToPathOptions, } from './prepend-namespace-to-path';

package/algorithms/config-generation/path-based-config-generator.d.ts

@@ -1,4 +1,4 @@
-import { LangTagCLIConfigGenerationEvent } from '../../config.ts';
+import { LangTagCLIConfigGenerationEvent } from '../../type';
 import { CaseType } from '../case-utils';
 export interface PathBasedConfigGeneratorOptions {
     /**

package/algorithms/config-generation/prepend-namespace-to-path.d.ts

@@ -1,4 +1,4 @@
-import { LangTagCLIConfigGenerationEvent } from '../../config.ts';
+import { LangTagCLIConfigGenerationEvent } from '../../type';
 /**
  * Options for the prependNamespaceToPath algorithm.
  */

package/algorithms/import/flexible-import-algorithm.d.ts

@@ -1,4 +1,4 @@
-import { LangTagCLIImportEvent } from '../../config.ts';
+import { LangTagCLIImportEvent } from '../../type';
 import { CaseType } from '../case-utils';
 /**
  * Available case transformation options for variable names.

package/algorithms/import/index.d.ts

@@ -4,5 +4,5 @@
  * These algorithms customize how library translations are imported
  * and organized in your project.
  */
-export { flexibleImportAlgorithm, type FlexibleImportAlgorithmOptions, type FilePathCaseType, type VariableNameCaseType } from './flexible-import-algorithm.ts';
-export { simpleMappingImportAlgorithm, type SimpleMappingImportAlgorithmOptions, type PackageMapping, type FileMapping } from './simple-mapping-import-algorithm.ts';
+export { flexibleImportAlgorithm, type FlexibleImportAlgorithmOptions, type FilePathCaseType, type VariableNameCaseType, } from './flexible-import-algorithm';
+export { simpleMappingImportAlgorithm, type SimpleMappingImportAlgorithmOptions, type PackageMapping, type FileMapping, } from './simple-mapping-import-algorithm';

package/algorithms/import/simple-mapping-import-algorithm.d.ts

@@ -1,4 +1,4 @@
-import { LangTagCLIImportEvent } from '../../config.ts';
+import { LangTagCLIImportEvent } from '../../type';
 /**
  * Mapping for a specific file within a package.
  * Defines which variables to import and optionally rename them.