docs: enhance installation and FAQ sections to clarify TypeScript and JavaScript options

Author: JeremyDolle

README.md

@@ -34,6 +34,14 @@ To create a new project using the boilerplate simply run :
 npx @react-native-community/cli@latest init MyApp --template @thecodingmachine/react-native-boilerplate
 ```
 
+During installation, you'll be asked:
+
+```
+📘 Using typescript ? (Y/n)
+```
+
+**Choose TypeScript (recommended)** or **Modern JavaScript (ESNext)** - the choice is yours! Both options provide the same architecture and features.
+
 Assuming you have all the requirements installed, you can run the project by running:
 
 - `yarn start` to start the metro bundler, in a dedicated terminal

documentation/docs/01-Getting Started.mdx

@@ -23,11 +23,27 @@ all while maintaining a clear separation of concerns.
 If you find value in this boilerplate, consider giving us a star. It would brighten our day like a ray of sunshine! 🌈☀️
 :::
 
+## TypeScript or JavaScript? You Choose! 🎯
+
+One of the most frequently requested features: **the boilerplate works with both TypeScript and Modern JavaScript (ESNext)!**
+
+During installation, you'll be prompted to choose:
+```bash
+📘 Using typescript ? (Y/n)
+```
+
+- **TypeScript (Default)**: Full type safety, enhanced IDE support, and better refactoring capabilities
+- **Modern JavaScript (ESNext/ES2022)**: Latest JavaScript features and syntax, automatically compiled from the TypeScript source
+
+Both options provide the **exact same architecture, features, and code organization**. The only difference is the language syntax.
+
+[Learn more about the installation process and language choice →](/docs/installation#using-the-boilerplate)
+
 ## Features
 
 | Features                                                               | Description                                                                                                                                                                                                                                     |
 | ---------------------------------------------------------------------- |------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
-| [`Javascript or TypeScript`](/docs/installation#using-the-boilerplate) | Every project, developer, team, and experience is unique. That's why you have the freedom to select either a JavaScript or TypeScript codebase. [The choice is yours!](/docs/installation#using-the-boilerplate)                                |
+| [`Javascript or TypeScript`](/docs/installation#using-the-boilerplate) | Every project, developer, team, and experience is unique. That's why you have the freedom to select either a Modern JavaScript (ESNext) or TypeScript codebase. [The choice is yours!](/docs/installation#using-the-boilerplate)                                |
 | [`Navigation`](/docs/navigate)                                         | With [React Navigation](https://reactnavigation.org/), we offer a swift start to your navigation structure through a robust dependency. Check out the details in our [navigation structure documentation](/docs/navigate#navigation-structure). |
 | [`Data fetching`](/docs/data-fetching)️                                 | Leveraging [TanStack Query](https://tanstack.com/query/latest), data fetching has never been this effortless, with a clean domain-based architecture.                                                                                           |
 | [`Internationalization`](/docs/internationalization)                   | Our application is fully prepared for multilingual support, all thanks to [React i18next](https://react.i18next.com/).                                                                                                                          |

documentation/docs/02-Installation.md

@@ -26,8 +26,37 @@ During the installation process, you will encounter the following prompt:
 📘 Using typescript ? (Y/n)
 ```
 
-This prompt gives you the flexibility to choose whether you want to use TypeScript or not.
-If you choose not to use TypeScript, the project will be created without any TypeScript configuration.
+This prompt gives you the flexibility to choose whether you want to use TypeScript or JavaScript for your project.
+
+### TypeScript (Default - Recommended)
+
+If you choose **Yes** (or simply press Enter), your project will be set up with TypeScript. This includes:
+- Full TypeScript support with strict type checking
+- Type definitions for all services, components, and hooks
+- Enhanced IDE autocomplete and error detection
+- Better refactoring capabilities
+
+### JavaScript
+
+If you choose **No**, the boilerplate will automatically:
+1. 📦 Install TypeScript temporarily as a build tool
+2. 🧱 Compile all TypeScript source files to JavaScript
+3. 🖼️ Copy assets (images, icons) to the compiled output
+4. ♻️ Replace the TypeScript source with the compiled JavaScript code
+5. 🌀 Remove TypeScript-specific files:
+   - Type definition files (`*.d.ts`)
+   - Type directories (`src/services/theme-generation/types/`)
+   - Navigation type files
+
+The resulting project will be pure JavaScript while maintaining the same architecture and structure.
+
+:::note ESLint Configuration
+The ESLint configuration is designed to work with both TypeScript and JavaScript projects. When using JavaScript, TypeScript-specific rules are automatically disabled.
+:::
+
+:::warning Migration Limitation
+Once you choose JavaScript, migrating back to TypeScript requires manual effort. Consider your team's preferences carefully before making this choice.
+:::
 
 ## Running the project
 

documentation/docs/04-Guides/09-ESLint.md

@@ -60,6 +60,37 @@ export default defineConfig([
 ]);
 ```
 
+### JavaScript Support
+
+The ESLint configuration works seamlessly with both TypeScript and JavaScript projects:
+
+```js title="eslint.config.js"
+export default defineConfig([
+  // ... TypeScript configs
+
+  // Specific configuration for JavaScript files
+  {
+    files: ['**/*.{js,jsx}'],
+    ...tseslint.configs.disableTypeChecked,
+  },
+
+  // ... rest of config
+]);
+```
+
+When you choose JavaScript during project initialization, TypeScript-specific type-checking rules are automatically disabled for `.js` and `.jsx` files. This includes:
+- All rules requiring type information (from `strictTypeChecked` and `stylisticTypeChecked`)
+- Type-aware linting rules
+
+**All other rules remain active for JavaScript:**
+- Project structure enforcement
+- Code composition rules
+- Import sorting (perfectionist)
+- React best practices
+- Unicorn JS/TS best practices
+
+This ensures code quality and architectural consistency regardless of whether you use TypeScript or JavaScript.
+
 ## Key Plugins
 
 ### 1. eslint-plugin-project-structure