@zohodesk/client_build_tool 0.0.1-0.exp.0.0.3

package/README.md

@@ -0,0 +1,184 @@
+# Client Build Tool
+
+This is a build tool for react based web applications.
+
+Supported and Tested Environment
+
+| Name | Version  |
+| :--: | :------: |
+| node | v18.11.0 |
+| npm  |  8.19.2  |
+
+OS : Mac , ubuntu
+
+# client_build_tool
+
+A CLI tool for build modern web application and libraries
+
+# Installation
+
+Below Steps:-
+
+> `npm i -g @zohodesk/client_build_tool`
+
+# Usage
+
+## Step 1
+
+> `cbt template app <your-project-folder> && cd <your-project-folder>`
+
+## Step 2
+
+Now to run app
+
+> `npm run start`
+
+---
+
+Happy Code :>) 🤟
+
+# "Client Build Tool (CBT): Streamline and Optimize Your Client-side Build Process"
+
+## Description:
+
+CBT is a powerful client-side build tool designed to streamline and optimize your development workflow. With CBT, you can effortlessly manage and configure your project's build process, automating tasks, and improving efficiency. It provides an intuitive interface and a comprehensive set of features to simplify the build pipeline, allowing you to focus more on coding and less on tedious configuration.
+
+## Key Features:
+
+- **Integrated Dev Server:** Run your application locally with a built-in development server for quick feedback and real-time updates.
+- **Mock API Server:** Seamlessly integrate a mock API server to simulate backend interactions during development.
+- **Intelligent CSS Processing:** Automatically process and optimize CSS files, including customizable class name generation and advanced postcss plugins.
+- **Internationalization Support:** Easily manage internationalization (i18n) with efficient chunk splitting and language-specific resource loading.
+- **CDN Mapping:** Effortlessly map assets to a Content Delivery Network (CDN) for faster delivery and improved performance.
+- **Comprehensive Configuration:** Fine-tune your build process with extensive configuration options, including source maps, Babel customizations, and more.
+- **Service Worker Integration:** Enable service worker functionality for offline support and improved caching capabilities.
+- **Customizable Build Artifacts:** Define custom chunks, modify HTML templates, and generate a manifest.json file for better control over your build output.
+- **User-friendly Interface:** CBT provides a user-friendly interface, making it easy to configure, customize, and monitor your build process.
+
+With CBT, you can optimize your client-side development workflow, increase productivity, and deliver high-quality applications faster. Start using CBT today and experience the power of efficient and streamlined client-side builds.
+
+# Commands
+
+The following commands are available options for the `cbt` (Client Build Tool) CLI. You can execute these commands by prefixing them with `cbt`. For example, `cbt start`.
+
+- **preProcessor:** Runs the preProcessor.js in the app to set the variables before the build or run the dev mode.
+
+- **start**: Starts the development server with mode support. You can specify the mode as either `dev` or `prod`. This command is used for local development and testing.
+
+- **build**: Executes the build command with mode support. You can specify the mode as either `dev` or `prod`. This command compiles and bundles your application for deployment.
+
+- **build:lib**: Transpile the `src` folder to the `lib` folder, generating CommonJS modules. This command is specifically designed for building libraries that require CommonJS module format.
+
+- **build:es**: Transpile the `src` folder to the `es` folder, generating modules using import statements. This command is useful for building libraries that use ECMAScript module syntax.
+
+- **version**: Prints the version of the CBT CLI tool.
+
+- **template**: Creates an initial template or skeleton for your project. You can specify the option as `app`. This command sets up a basic project structure and configuration files to get you started quickly.
+
+- **mock:server**: Starts an external mock API server. This command enables you to run a separate server specifically for mocking API responses during development and testing.
+
+> Note: Make sure to replace `start` in the examples above with the actual command or script that you use to run the Client Build Tool CLI.
+
+These commands provide flexibility and control over your client-side build process, allowing you to start the development server, build your application, transpile libraries, create templates, run a mock API server, and more.
+
+For more [Details](ConfigurationDocumentation.md)
+
+
+version details :- 
+
+# 0.0.8 
+
+- Main version 
+
+# 0.0.9 
+
+fixes :- 
+
+- service worker wrong i18n entry fixed 
+
+- preload plc undefined url fixed 
+
+# Changelog and Release Notes
+# v0.0.10 (12-05-2025)
+**Feature:-**
+- `alias` support for `build:es` and `build:lib`
+    - Add babel-plugin-module-resolver dependencies
+    - Modify getBabelPlugin to include module resolver with aliases
+
+**Bug Fix:-**
+- Enhance runBabelForTSFile to handle both .tsx and .ts file extensions
+- Update mockApiHandler to ensure mock function is called correctly
+
+**Change:-**
+- Refactor defaultConfigValues.js to include cli options for enableRTLSplit
+
+**Feature:-**
+- externals was added to  Prevent bundling of certain imported packages and retrieve these external dependencies at runtime.
+- to use externals, we use the following pattern in `app > externals` :
+
+For example
+```
+   externals: {
+    <key> : <value>
+   }
+```
+
+## v0.0.6 (4-09-2023)
+
+**Feature:-**
+- Generating bundle integrity report json file for the build assets only in production mode. To use this feature we need to add `stats > enable` or cli flags `enable_stats`.
+- Added Resource Cleanup plugin to cleanup resource retained by build tool. this plugin is controlled by efc flag resourcecleanup flag.
+- added support for using regex expression to get group of chunks chunkId via Resource Hint plugin prefetch/preload hook.
+  only will be activate when `resourceHints` => `allowPrefetchingMultipleChunks` as `true`
+- added support for glob pattern for custom chunks split logic.
+- added options to split chunks base config in the key `app` => `customChunksBaseConfig` as object
+
+**Change:-**
+- i18n name not generated issue fix.
+- public path not correctly set issue fix.
+- changing plugin hook stages in i18nRuntimePlugin and sourceMapPlugin
+## v0.0.5 (6-08-2023)
+
+**Changes:--**
+- Typo fix in i18nRuntimeDealerPlugin.js
+- fixing some bugs in resolvers.js file
+
+## v0.0.3 (1-08-2023)
+
+**Changes:--**
+- `devtool` default value changed from `hidden-cheap-source-map` to `source-map`
+- unwanted files deleted from build
+
+**Issue Fix:--**
+- The issue with the source map not being created in the build has been fixed."
+
+
+## v0.0.2 (28-04-2023)
+
+**Features:-**
+
+- `devModeContentHashAllowedTypes` support added for some project there will be a need for hash even though they run dev mode. for details [details](https://zgit.csez.zohocorpin.com/zohodesk/react-cli/-/blob/3.0.0/packages/client_build_tool/ConfigurationDocumentation.md#devModeContentHashAllowedTypes)
+- `devLikeHash` support for disable content hash for file names in production mode. for details [details](https://zgit.csez.zohocorpin.com/zohodesk/react-cli/-/blob/3.0.0/packages/client_build_tool/ConfigurationDocumentation.md#devLikeHash)
+- `disableReactDevWarning` disable react dev warning such as prop-type warnings will be removed in dev mode build or server. for details [details](https://zgit.csez.zohocorpin.com/zohodesk/react-cli/-/blob/3.0.0/packages/client_build_tool/ConfigurationDocumentation.md#disableReactDevWarning) can be enabled via `--disable_react_dev_warning` too.
+- `statsLogConfig` support to customize default webpack log after build finished. for details [details](https://zgit.csez.zohocorpin.com/zohodesk/react-cli/-/blob/3.0.0/packages/client_build_tool/ConfigurationDocumentation.md#statsLogConfig) can be enabled via `--disable_react_dev_warning` too.
+- `enableChunkHash` renamed as `enableFileNameHashing`
+
+- `pre_processor` command to run the preprocessor.js file.preProcessor runs in build, start, buildEs, buildLib commands bu default. and we have watch mode support as well with the option (`-w`)
+- `createSeparateSmap` flag `source_map_enable` renamed as `enable_smap`
+- `removeAttribute` option changes as `babelCustomizations.removeAttribute`
+- `removePropTypes` support for remove the prop types package in the output build.
+- `devConsoleExclude` support for remove the _console statements_ such as _console.log_, _console.warn_ in the output build.
+- `manifestJson` default value set as false.
+- `customAttributes` support for add attributes to html, link , script tag in the output build.
+
+
+## v0.0.1 (18-04-2023)
+
+First Release
+**Features:-**
+
+- 'start' command to run react app
+- 'build' command to create build for react app
+- 'build:lib' command to create lib for react library
+- 'build:es' command to create es for react library
+- 'templates' command to create es for react library

package/README_backup.md

@@ -0,0 +1,100 @@
+# Client Build Tool
+
+This is a build tool for react based web applications.
+
+Supported and Tested Environment
+
+| Name | Version  |
+| :--: | :------: |
+| node | v18.11.0 |
+| npm  |  8.19.2  |
+
+OS : Mac , ubuntu
+
+# client_build_tool
+
+A CLI tool for build modern web application and libraries
+
+# Installation
+
+Below Steps:-
+
+> `npm i -g @zohodesk/client_build_tool`
+
+# Usage
+
+## Step 1
+
+> `cbt template app <your-project-folder> && cd <your-project-folder>`
+
+## Step 2
+
+Now to run app
+
+> `npm run start`
+
+---
+
+Happy Code :>) 🤟
+
+# "Client Build Tool (CBT): Streamline and Optimize Your Client-side Build Process"
+
+## Description:
+
+CBT is a powerful client-side build tool designed to streamline and optimize your development workflow. With CBT, you can effortlessly manage and configure your project's build process, automating tasks, and improving efficiency. It provides an intuitive interface and a comprehensive set of features to simplify the build pipeline, allowing you to focus more on coding and less on tedious configuration.
+
+## Key Features:
+
+- **Integrated Dev Server:** Run your application locally with a built-in development server for quick feedback and real-time updates.
+- **Mock API Server:** Seamlessly integrate a mock API server to simulate backend interactions during development.
+- **Intelligent CSS Processing:** Automatically process and optimize CSS files, including customizable class name generation and advanced postcss plugins.
+- **Internationalization Support:** Easily manage internationalization (i18n) with efficient chunk splitting and language-specific resource loading.
+- **CDN Mapping:** Effortlessly map assets to a Content Delivery Network (CDN) for faster delivery and improved performance.
+- **Comprehensive Configuration:** Fine-tune your build process with extensive configuration options, including source maps, Babel customizations, and more.
+- **Service Worker Integration:** Enable service worker functionality for offline support and improved caching capabilities.
+- **Customizable Build Artifacts:** Define custom chunks, modify HTML templates, and generate a manifest.json file for better control over your build output.
+- **User-friendly Interface:** CBT provides a user-friendly interface, making it easy to configure, customize, and monitor your build process.
+
+With CBT, you can optimize your client-side development workflow, increase productivity, and deliver high-quality applications faster. Start using CBT today and experience the power of efficient and streamlined client-side builds.
+
+# Commands
+
+The following commands are available options for the `cbt` (Client Build Tool) CLI. You can execute these commands by prefixing them with `cbt`. For example, `cbt start`.
+
+- **preProcessor:** Runs the preProcessor.js in the app to set the variables before the build or run the dev mode.
+
+- **start**: Starts the development server with mode support. You can specify the mode as either `dev` or `prod`. This command is used for local development and testing.
+
+- **build**: Executes the build command with mode support. You can specify the mode as either `dev` or `prod`. This command compiles and bundles your application for deployment.
+
+- **build:lib**: Transpile the `src` folder to the `lib` folder, generating CommonJS modules. This command is specifically designed for building libraries that require CommonJS module format.
+
+- **build:es**: Transpile the `src` folder to the `es` folder, generating modules using import statements. This command is useful for building libraries that use ECMAScript module syntax.
+
+- **version**: Prints the version of the CBT CLI tool.
+
+- **template**: Creates an initial template or skeleton for your project. You can specify the option as `app`. This command sets up a basic project structure and configuration files to get you started quickly.
+
+- **mock:server**: Starts an external mock API server. This command enables you to run a separate server specifically for mocking API responses during development and testing.
+
+> Note: Make sure to replace `start` in the examples above with the actual command or script that you use to run the Client Build Tool CLI.
+
+These commands provide flexibility and control over your client-side build process, allowing you to start the development server, build your application, transpile libraries, create templates, run a mock API server, and more.
+
+For more [Details](ConfigurationDocumentation.md)
+
+
+version details :- 
+
+# 0.0.8 
+
+- Main version 
+
+# 0.0.9 
+
+fixes :- 
+
+- service worker wrong i18n entry fixed 
+
+- preload plc undefined url fixed 
+

package/TODO.md

@@ -0,0 +1,35 @@
+
+
+
+[*] public  path  check template
+[ ] public  path dev build  url and  url less, prod url less  check 
+[ ] initial  html similarity check
+[ ] initial chunks check  ,
+[ ] initial efc chunks check 
+[ ] efc creation check 
+[ ] css tag order check
+[*] css tags creation check 
+
+10 Aug 2023
+[ ] enableFileNameHashing to dev mode for conflicting  svg files.
+[ ] customLoaders
+[ ] preprocess runner same as react-cli need to run. 
+[ ] need to  check  about `i18nChunkSplit:propertiesPattern`
+[*] need to check `publicPaths` for cbt same as react-cli need to run. we can use CDN Mapping
+
+8 Apr 2023
+
+[*]  `HIGH` react-cli global modulePath and global certificate  
+[ ]   `Low`  Docs separation
+
+
+
+every folders must have unit testcases, only 100%
+
+code for newbie edit already exits code 
+testing startagy
+
+
+
+KT react-cli 
+* 

package/cli.js

@@ -0,0 +1,31 @@
+#!/usr/bin/env node
+
+const { polyfillForOldNodeVersion } = require('./polyfillForOldNodeVersion');
+
+polyfillForOldNodeVersion();
+
+const { verboseLogger } = require('./lib/logger');
+const { route } = require('./lib/commandsRouter');
+const {
+  readArgsFormCommandLine,
+  readOptionFormCommandLine,
+  doBasicRequirementCheck
+} = require('./lib/shared/commands-utils');
+const { versionPrint } = require('./lib/shared/utils/versionPrint');
+
+// process.traceDeprecation = true;
+
+verboseLogger('hello there, this is client build tool verbose logging..');
+versionPrint(verboseLogger);
+
+const option = readOptionFormCommandLine();
+const args = readArgsFormCommandLine();
+
+// // like  machine support  and  node  support  and  npm support
+// //  if it is ok then do the proper work.
+
+if (doBasicRequirementCheck()) {
+  // runProperCommand(option, args)
+  verboseLogger(`the command was ${option}`, args);
+  route(option);
+}

package/docs/BabelCustomizations.md

@@ -0,0 +1,55 @@
+## Babel Customizations Configuration Documentation
+
+The `babelCustomizations` object in the provided code represents a set of customizations that can be applied to the Babel configuration within the context of the Client Build Tool (CBT). These customizations allow you to fine-tune how JavaScript code is transpiled and transformed during the build process. Below is the documentation for the individual customizations:
+
+### babelCustomizations.browserList
+
+> Type: (null or string array)
+
+This configuration option allows you to define a custom `browserslist` for Babel, which specifies the targeted browsers and their versions. If set to `null`, the default `browserslist` of the environment will be used.
+
+### babelCustomizations.removeAttribute
+
+This customization is used to remove specific HTML attributes from JSX elements during transpilation.
+
+- **enable** (boolean): Determines whether the removal of attributes is enabled (`true`) or not (`false`).
+
+- **options** (object): Contains settings related to attribute removal.
+
+  - **attributeNames** (string array): Specifies the names of HTML attributes that should be removed from JSX elements during transpilation.
+
+### babelCustomizations.removePropTypes
+
+This customization is used to remove `prop-types` declarations from React components.
+
+- **enable** (boolean): Determines whether the removal of `prop-types` is enabled (`true`) or not (`false`).
+
+- **options** (object): Contains settings related to `prop-types` removal.
+
+  - **mode** ('remove'): Specifies the removal mode. Currently, only `'remove'` mode is supported.
+
+  - **removeImport** (boolean): Determines whether the import statement for `prop-types` should also be removed when `prop-types` declarations are removed.
+
+### babelCustomizations.devConsoleExclude
+
+This customization is used to exclude certain types of console messages from the build output in development mode.
+
+- **enable** (boolean or object): If a boolean, determines whether console message exclusion is enabled (`true`) or not (`false`). If an object, it can have two properties:
+
+  - **value** (boolean): Determines whether the exclusion is enabled (`true`) or not (`false`).
+
+  - **cli** (string): Provides an option to control the behavior through the CLI by using the specified command line argument.
+
+- **options** (object): Contains settings related to console message exclusion.
+
+  - **exclude** (string array): Specifies the types of console messages that should be excluded from the build output. For example, `['error', 'warn']` would exclude both error and warning messages.
+
+### babelCustomizations.plugins
+
+> Type: (array)
+
+This customization allows you to specify an array of Babel plugins that will be applied during transpilation.
+
+- **plugins** (array): An array of Babel plugins that will be used for transpilation.
+
+By customizing the `babelCustomizations` configuration, you can tailor the Babel transpilation process to meet the specific requirements of your project, such as removing certain attributes, optimizing for development console messages, or adding custom Babel plugins.

package/docs/CSSCustomPluginsDocumentation.md

@@ -0,0 +1,71 @@
+## CSS Custom Plugins Documentation
+
+The following documentation provides an overview of the CSS custom plugins available in the Client Build Tool (CBT) configuration. These plugins allow you to extend the functionality of PostCSS, a powerful tool for transforming CSS using JavaScript plugins. Each plugin can be customized based on your specific requirements. Here are the available CSS custom plugins:
+
+### rtlSplit
+
+- **enableRTLSplit** (boolean): Specifies whether to enable Right-to-Left (RTL) splitting. When enabled, this plugin generates separate CSS files for RTL layouts. The default value is `false`.
+
+- **templateLabel** (string): Specifies the template label used for RTL splitting. The default value is `'{{--dir}}'`.
+
+- **disableMinifySelector** (boolean): Specifies whether to disable minification of CSS selectors during RTL splitting. The default value is `false`.
+
+- **dirVarName** (string): Specifies the variable name used to store the direction (LTR or RTL). The default value is `'document.dir'`.
+
+### selectorWeight
+
+- **enable** (boolean): Specifies whether to enable the selector weight plugin. When enabled, this plugin calculates the weight of CSS selectors based on specificity. The default value is `false`.
+
+- **patterns** (array): Specifies an array of file patterns to apply the selector weight plugin. The default value is an empty array.
+
+- **configFile** (null): Specifies the configuration file for the selector weight plugin. The default value is `null`.
+
+- **defaultSelector** (string): Specifies the default selector used by the selector weight plugin. The default value is an empty string.
+
+- **customFileDetails** (string): Specifies custom file details for the selector weight plugin. The default value is an empty string.
+
+- **excludeStrings** (array): Specifies an array of strings to exclude from the selector weight calculations. The default value is an empty array.
+
+### valueReplacer
+
+- **enable** (boolean): Specifies whether to enable the value replacer plugin. When enabled, this plugin replaces values in CSS properties based on specified patterns. The default value is `false`.
+
+- **patterns** (array): Specifies an array of patterns to match CSS property values for replacement. The default value is an empty array.
+
+- **config** (array): Specifies an array of configuration options for the value replacer plugin. The default value is an empty array.
+
+### selectorReplace
+
+- **enable** (boolean): Specifies whether to enable the selector replace plugin. When enabled, this plugin replaces CSS selectors based on specified patterns. The default value is `false`.
+
+- **patterns** (array): Specifies an array of patterns to match CSS selectors for replacement. The default value is an empty array.
+
+- **before** (array): Specifies an array of strings or regular expressions to match selector patterns that should be replaced before the main replacement. The default value is an empty array.
+
+- **after** (array): Specifies an array of strings or regular expressions to match selector patterns that should be replaced after the main replacement. The default value is an empty array.
+
+### hoverActive
+
+- **enable** (boolean): Specifies whether to enable the hover and active plugin. When enabled, this plugin generates CSS for hover and active states based on specified patterns. The default value is `false`.
+
+- **patterns** (array): Specifies an array of patterns to match CSS selectors for generating hover and active states. The default value is an empty array.
+
+- **hover** (string): Specifies the CSS pseudo-class for the hover state. The default value is `'(hover: hover)'`.
+
+- **active** (string): Specifies the CSS pseudo-class for the active state. The default value is `'(hover: none)'`.
+
+### cssVariableReplacement
+
+- **enable** (boolean): Specifies whether to enable the CSS variable replacement plugin. When enabled, this plugin replaces CSS variables based on specified patterns. The default value is `false`.
+
+- **patterns** (array): Specifies an array of patterns to match CSS variable names for replacement. The default value is an empty array.
+
+- **configFile** (null): Specifies the configuration file for the CSS variable replacement plugin. The default value is `null`.
+
+### rtl
+
+- **enable** (boolean): Specifies whether to enable the RTL plugin. When enabled, this plugin generates RTL-specific CSS based on specified patterns. The default value is `false`.
+
+- **patterns** (array): Specifies an array of patterns to match CSS selectors for RTL transformation. The default value is an empty array.
+
+These custom plugins provide additional functionality and customization options for transforming CSS during the build process. You can enable or disable each plugin as needed and configure them according to your project's requirements.

package/docs/MockApi.md

@@ -0,0 +1,61 @@
+# Mock Api
+
+## Explanation:-
+
+    This api is for run mock api.
+    The reason for this feature is we usually run dev server as just to server react page not for api request.
+    So when we need Mock Api or api request related this not on server (some java server).
+    But do it in node js, this api.
+
+## Ways to use Mock api
+
+    There is two ways to run mock api.
+
+1. Run mock api with dev server
+2. Run mock api separate from dev server but api can be called through dev server.
+
+### Run mock api with dev server
+
+    In this way of running you do not need to run extra you do not have to run separate command.
+    But every change you do in mock api you need to stop and restart.
+
+To run this you have to enable mock server and just un dev server as usual `cbt start`
+
+### Run mock api separate from dev server
+
+    This api is for run mock api in separate nodemon.
+
+So to run this you have to enable mock api and run `cbt mock:server`.
+
+## Configuration
+
+To config this mock api
+you can need to add `mockServer` key in **cbt.config.js** or **package.json** file (`client-build-config` or `react-cli`) ==> `mockServer`
+
+|      option       |  type   |     default      |
+| :---------------: | :-----: | :--------------: |
+|      enable       | Boolean |      false       |
+| separateSeverPort | Number  |       null       |
+|  disableNodemon   | Boolean |      false       |
+|   mockEntryFile   | String  | mockapi/index.js |
+|    mockPrefix     | String  |      /api/       |
+
+### **enable**:
+
+Specifies whether the application's mocking functionality is enabled or disabled. When set to `true`, the application will use the mock server. When set to `false`, the mock server will be disabled. By default, the value is set to `false`.
+
+### **separateSeverPort**:
+
+Specifies the port to be used by the mock server. If the `enable` option is set to `true`, the application will use this port to run the mock server. This configuration parameter should be set to a valid port number. In this case, the port number is set to `8080`.
+
+### **disableNodemon**:
+
+Specifies whether nodemon, a utility that automatically restarts the application upon file changes, should be disabled. When set to `true`, nodemon will be disabled. When set to `false`, nodemon will remain enabled. By default, the value is set to `false`.
+
+### **mockEntryFile**:
+
+Specifies the entry file for the mock server. This file is the starting point for the mock server's execution. The value should be a string representing the file path. In this case, the entry file is set to `mockapi/index.js`.
+
+### **mockPrefix**:
+
+Specifies the URL prefix for the mock server's API endpoints. The value should be a string representing the desired prefix. In this case, the prefix is set to `/api/`.

package/docs/NameTemplateUtility.md

@@ -0,0 +1,93 @@
+## Name Template Utility Documentation
+
+The provided code snippet represents a utility module for generating name templates used in the build process of the Client Build Tool (CBT). The module contains functions for creating name templates and determining whether a file is an internationalization file. Let's document the different parts of the code:
+
+### Import Statements
+
+```javascript
+import { isDevelopmentMode, isProductionMode } from './modeUtils';
+```
+
+This import statement brings in the `isDevelopmentMode` and `isProductionMode` functions from the `modeUtils` module.
+
+### Templates Object
+
+The `templates` object represents a collection of different name templates used for various types of files during the build process. Each key-value pair in the object represents a file type and its corresponding name templates.
+
+### createNameTemplate Function
+
+The `createNameTemplate` function is used to generate a name template for a specific file type based on whether a hash should be included in the file name. It takes in the `name` and `useHash` parameters and returns the appropriate name template based on the `useHash` value.
+
+### nameTemplates Function
+
+The `nameTemplates` function is a utility function that determines the name template for a specified file type based on the provided options. It takes in the `type` and `options` parameters and returns the corresponding name template.
+
+### isI18nFile Function
+
+The `isI18nFile` function is a utility function that checks whether a given URL represents an internationalization file. It takes in the `url` parameter and returns `true` if the URL ends with `.i18n.js`, indicating it is an internationalization file.
+
+### Export Statements
+
+The module exports the `nameTemplates` function, allowing it to be used in other parts of the build process. The `isI18nFile` function is not exported and is intended for internal use within the module.
+
+By using these utility functions, you can generate name templates for different types of files during the build process. These name templates play a crucial role in determining the output file names and paths, enabling effective asset management and caching strategies.
+
+Please note that the provided code snippet represents a partial implementation, and there may be additional code or dependencies required for the utility module to function correctly within the overall CBT system.
+
+## File Templates Configuration Documentation
+
+The `templates` object in the provided code represents a collection of file templates used in the build process of the Client Build Tool (CBT). The object contains various file types as keys, and each key holds an array of file templates for development and production modes. Here is the documentation for the file templates:
+
+```javascript
+const templates = {
+  html: ['index.html', 'index.[contenthash].html'],
+  js: ['js/[name].js', 'js/[name].[contenthash].js'],
+  chunkjs: ['js-chunks/[name].js', 'js-chunks/[name].[contenthash].js'],
+  i18njs: [
+    'i18n-chunks/[locale]/[name].i18n.js',
+    'i18n-chunks/[locale]/[name].[chunkhash].i18n.js'
+  ],
+  i18nchunkjs: [
+    'i18n-chunks/[locale]/[name].i18n.js',
+    // 'i18n-chunks/[locale]/[name].[chunkhash].i18n.js'
+    'i18n-chunks/[locale]/[name].[contenthash].i18n.js'
+  ],
+  i18nmanifest: ['i18n-manifest.json', 'i18n-manifest.json'],
+  workerjs: ['js/[name].js', 'js/[name].[contenthash].js'],
+  css: ['css/[name].css', 'css/[name].[contenthash].css'],
+  cssdir: ['css/[name].[dir].css', 'css/[name].[contenthash].[dir].css'],
+  image: ['images/[name][ext]', 'images/[name].[contenthash][ext]'],
+  font: ['fonts/[name][ext]', 'fonts/[name].[contenthash][ext]'],
+  svg: ['fonts/[name][ext]', 'fonts/[name].[contenthash][ext]'],
+  audio: ['fonts/[name][ext]', 'fonts/[name].[contenthash][ext]'],
+  video: ['videos/[name][ext]', 'videos/[name].[contenthash][ext]']
+};
+```
+
+The `templates` object contains file templates for various types of assets used in the build process. Each key-value pair represents a file type and its corresponding file templates.
+
+Here are some key points regarding the file templates:
+
+- **html**: Contains file templates for HTML files. The development mode template is `'index.html'`, and the production mode template includes a `[contenthash]` placeholder, resulting in `'index.[contenthash].html'`.
+
+- **js**: Contains file templates for JavaScript files. The development mode template is `'js/[name].js'`, where `[name]` is replaced by the actual name of the JavaScript file. The production mode template includes a `[contenthash]` placeholder, resulting in `'js/[name].[contenthash].js'`.
+
+- **chunkjs**: Contains file templates for chunk JavaScript files. The templates follow a similar pattern to the `js` templates.
+
+- **i18njs**: Contains file templates for internationalization JavaScript files. The templates include a `[locale]` placeholder, representing the locale, and a `[chunkhash]` placeholder in the production mode template.
+
+- **i18nchunkjs**: Contains alternative file templates for internationalization JavaScript files. The production mode template uses a `[contenthash]` placeholder instead of `[chunkhash]`.
+
+- **i18nmanifest**: Contains file templates for the internationalization manifest file. The same template is used for both development and production modes.
+
+- **workerjs**: Contains file templates for worker JavaScript files. The templates follow a similar pattern to the `js` templates.
+
+- **css**: Contains file templates for CSS files. The templates follow a similar pattern to the `js` templates.
+
+- **cssdir**: Contains file templates for CSS files with directory placeholders. The templates include a `[dir]` placeholder in the file name. Changing this line may affect other files and plugins in the build process.
+
+- **image**, **font**, **svg**, **audio**, **video**: Contains file templates for different types of static assets. The templates follow specific patterns based on the file extensions and include placeholders like `[name]`, `[contenthash]`, and `[ext]` to generate dynamic file names.
+
+These file templates are used by the build process to determine the output file names and paths for different assets. They allow for effective asset management and caching strategies during development and production modes.
+
+Please note that the provided code snippet represents a partial implementation, and there may be additional code or dependencies required to fully utilize the file templates within the overall CBT system.