optikit 1.0.1

package/.history/.gitignore_20241023143139

@@ -0,0 +1,53 @@
+# Node.js modules
+node_modules/
+
+# Build output
+dist/
+
+# Log files
+*.log
+
+# Environment variables
+.env
+.env.local
+.env.*.local
+
+# Temporary files
+*.tmp
+*.temp
+*.cache
+
+# IDE and Editor folders
+.idea/
+.vscode/
+.DS_Store
+
+# TypeScript output
+*.tsbuildinfo
+*.js
+*.d.ts
+
+# Ignore package-lock.json
+package-lock.json
+
+# Yarn specific files
+yarn-error.log
+yarn-debug.log
+
+# OS specific files
+Thumbs.db
+ehthumbs.db
+Icon?
+Desktop.ini
+
+# Coverage directory used by tools like istanbul
+coverage/
+
+# Jest test results
+jest-test-results.json
+
+# NPM local config
+.npm/
+
+# npm-debug.log
+npm-debug.log*

package/.history/.gitignore_20241024014912

@@ -0,0 +1,54 @@
+# Node.js modules
+node_modules/
+
+# Build output
+dist/
+
+# Log files
+*.log
+
+# Environment variables
+.env
+.env.local
+.env.*.local
+
+# Temporary files
+*.tmp
+*.temp
+*.cache
+
+# IDE and Editor folders
+.idea/
+.vscode/
+.DS_Store
+
+# TypeScript output
+*.tsbuildinfo
+*.js
+*.d.ts
+
+# Ignore package-lock.json
+package-lock.json
+
+# Yarn specific files
+yarn-error.log
+yarn-debug.log
+
+# OS specific files
+Thumbs.db
+ehthumbs.db
+Icon?
+Desktop.ini
+
+# Coverage directory used by tools like istanbul
+coverage/
+
+# Jest test results
+jest-test-results.json
+
+# NPM local config
+.npm/
+
+# npm-debug.log
+npm-debug.log*
+

package/.history/.gitignore_20241024014914

@@ -0,0 +1,55 @@
+# Node.js modules
+node_modules/
+
+# Build output
+dist/
+
+# Log files
+*.log
+
+# Environment variables
+.env
+.env.local
+.env.*.local
+
+# Temporary files
+*.tmp
+*.temp
+*.cache
+
+# IDE and Editor folders
+.idea/
+.vscode/
+.DS_Store
+
+# TypeScript output
+*.tsbuildinfo
+*.js
+*.d.ts
+
+# Ignore package-lock.json
+package-lock.json
+
+# Yarn specific files
+yarn-error.log
+yarn-debug.log
+
+# OS specific files
+Thumbs.db
+ehthumbs.db
+Icon?
+Desktop.ini
+
+# Coverage directory used by tools like istanbul
+coverage/
+
+# Jest test results
+jest-test-results.json
+
+# NPM local config
+.npm/
+
+# npm-debug.log
+npm-debug.log*
+
+#

package/.history/.gitignore_20241024014915

@@ -0,0 +1,55 @@
+# Node.js modules
+node_modules/
+
+# Build output
+dist/
+
+# Log files
+*.log
+
+# Environment variables
+.env
+.env.local
+.env.*.local
+
+# Temporary files
+*.tmp
+*.temp
+*.cache
+
+# IDE and Editor folders
+.idea/
+.vscode/
+.DS_Store
+
+# TypeScript output
+*.tsbuildinfo
+*.js
+*.d.ts
+
+# Ignore package-lock.json
+package-lock.json
+
+# Yarn specific files
+yarn-error.log
+yarn-debug.log
+
+# OS specific files
+Thumbs.db
+ehthumbs.db
+Icon?
+Desktop.ini
+
+# Coverage directory used by tools like istanbul
+coverage/
+
+# Jest test results
+jest-test-results.json
+
+# NPM local config
+.npm/
+
+# npm-debug.log
+npm-debug.log*
+
+# 

package/.history/.gitignore_20241024014921

@@ -0,0 +1,56 @@
+# Node.js modules
+node_modules/
+
+# Build output
+dist/
+
+# Log files
+*.log
+
+# Environment variables
+.env
+.env.local
+.env.*.local
+
+# Temporary files
+*.tmp
+*.temp
+*.cache
+
+# IDE and Editor folders
+.idea/
+.vscode/
+.DS_Store
+
+# TypeScript output
+*.tsbuildinfo
+*.js
+*.d.ts
+
+# Ignore package-lock.json
+package-lock.json
+
+# Yarn specific files
+yarn-error.log
+yarn-debug.log
+
+# OS specific files
+Thumbs.db
+ehthumbs.db
+Icon?
+Desktop.ini
+
+# Coverage directory used by tools like istanbul
+coverage/
+
+# Jest test results
+jest-test-results.json
+
+# NPM local config
+.npm/
+
+# npm-debug.log
+npm-debug.log*
+
+# .history directory
+.history/

package/.history/.npmignore_20241205005905

@@ -0,0 +1,4 @@
+node_modules/
+dist/
+*.log
+test/

package/.history/.npmignore_20241205005909

@@ -0,0 +1,4 @@
+node_modules/
+dist/
+*.log
+test/

package/.history/.npmignore_20241205005925

@@ -0,0 +1,4 @@
+node_modules/
+dist/
+*.log
+test/

package/.history/CHANGELOG_20250202181744.md

@@ -0,0 +1,34 @@
+# Changelog
+
+All notable changes to this project are documented in this file. Each release includes details about new features, improvements, bug fixes, and any breaking changes. This changelog helps users and developers track the evolution of the project and understand how different versions may impact their use of the tool.
+
+We follow Semantic Versioning (SemVer) to indicate the nature of changes:
+
+	•	MAJOR: Breaking changes that may affect compatibility.
+	•	MINOR: New features or improvements that are backward compatible.
+	•	PATCH: Bug fixes and minor improvements that are backward compatible.
+
+Each section lists the changes in chronological order, with the most recent release at the top. We also include links to relevant discussions or issues when appropriate.
+
+## [1.1.0] - 2024-11-21
+### Added
+- New Commands:
+  - `optikit flutter-update-version`: Update the version and build numbers for both Android and iOS, with support for automatic versioning and build number management.
+  - `optikit flutter-build-ios`: Build the Flutter iOS app for release, with support for FVM and automatic version incrementing
+  - `optikit flutter-build-ipa`: Create a release IPA for the Flutter app, with support for FVM and automatic version incrementing.
+
+## [1.0.0] - 2024-11-18
+### Added
+- Initial release of the CLI tool with the following commands:
+  - `optikit generate module <module_name>`
+  - `optikit clean-flutter`
+  - `optikit clean-ios`
+  - `sheno flutter-build-apk`
+  - `sheno flutter-build-bundle`
+  - `sheno open-android`
+  - `sheno open-ios`
+- Support for version handling using Semantic Versioning (SemVer).
+
+## [0.1.0] - 2024-10-15
+### Added
+- Initial prototype with basic CLI command structure.

package/.history/CHANGELOG_20250202181748.md

@@ -0,0 +1,34 @@
+# Changelog
+
+All notable changes to this project are documented in this file. Each release includes details about new features, improvements, bug fixes, and any breaking changes. This changelog helps users and developers track the evolution of the project and understand how different versions may impact their use of the tool.
+
+We follow Semantic Versioning (SemVer) to indicate the nature of changes:
+
+	•	MAJOR: Breaking changes that may affect compatibility.
+	•	MINOR: New features or improvements that are backward compatible.
+	•	PATCH: Bug fixes and minor improvements that are backward compatible.
+
+Each section lists the changes in chronological order, with the most recent release at the top. We also include links to relevant discussions or issues when appropriate.
+
+## [1.1.0] - 2024-11-21
+### Added
+- New Commands:
+  - `optikit flutter-update-version`: Update the version and build numbers for both Android and iOS, with support for automatic versioning and build number management.
+  - `optikit flutter-build-ios`: Build the Flutter iOS app for release, with support for FVM and automatic version incrementing
+  - `optikit flutter-build-ipa`: Create a release IPA for the Flutter app, with support for FVM and automatic version incrementing.
+
+## [1.0.0] - 2024-11-18
+### Added
+- Initial release of the CLI tool with the following commands:
+  - `optikit generate module <module_name>`
+  - `optikit clean-flutter`
+  - `optikit clean-ios`
+  - `optikit flutter-build-apk`
+  - `optikit flutter-build-bundle`
+  - `optikit open-android`
+  - `optikit open-ios`
+- Support for version handling using Semantic Versioning (SemVer).
+
+## [0.1.0] - 2024-10-15
+### Added
+- Initial prototype with basic CLI command structure.

package/.history/CHANGELOG_20250202181814.md

@@ -0,0 +1,4 @@
+
+## [0.1.0] - 2024-10-15
+### Added
+- Initial prototype with basic CLI command structure.

package/.history/CHANGELOG_20250202181815.md

@@ -0,0 +1,3 @@
+## [0.1.0] - 2024-10-15
+### Added
+- Initial prototype with basic CLI command structure.

package/.history/CHANGELOG_20250202181821.md

@@ -0,0 +1,3 @@
+## [0.1.0]
+### Added
+- Initial prototype with basic CLI command structure.

package/.history/CHANGELOG_20250202181824.md

@@ -0,0 +1,3 @@
+## [1.1.0]
+### Added
+- Initial prototype with basic CLI command structure.

package/.history/CHANGELOG_20250202181825.md

@@ -0,0 +1,3 @@
+## [1.0.0]
+### Added
+- Initial prototype with basic CLI command structure.

package/.history/CHANGELOG_20250202181827.md

@@ -0,0 +1,3 @@
+## [1.0.0]
+### Added
+- Initial prototype with basic CLI command structure.

package/.history/INSTALLATION_20250202181653.md

@@ -0,0 +1,118 @@
+# Installation Guide for OptiKit CLI
+
+This guide provides various methods to install the **Sheno CLI Tool**. Whether you prefer installing via NPM, cloning the repository, or using Homebrew, choose the method that best suits your setup.
+
+---
+
+## Install via NPM
+
+The easiest and most straightforward way to install the **Sheno CLI** is by using NPM. This method works on all platforms (macOS, Linux, and Windows).
+
+### Steps:
+1. Run the following command to install the CLI globally:
+   ```bash
+   npm install -g sheno_cli
+   ```
+
+2. Verify the installation:
+   ```bash
+   sheno --version
+   ```
+
+---
+
+## Install via Repository Clone
+
+For users who want to work with the source code directly, you can clone the repository and build it locally.
+
+### Steps:
+1. Clone the repository:
+   ```bash
+   git clone https://github.com/dev-mahmoud-elshenawy/sheno_cli.git
+   cd sheno_cli
+   ```
+
+2. Install dependencies and build the project:
+   ```bash
+   npm install && npm run build
+   ```
+
+3. Add the CLI to your PATH (based on your operating system):
+   - **macOS**:
+     ```bash
+     echo 'export PATH="$PATH:/your_path/sheno_cli"' >> ~/.zshrc
+     source ~/.zshrc
+     ```
+   - **Linux**:
+     ```bash
+     echo 'export PATH="$PATH:/your_path/sheno_cli"' >> ~/.bashrc
+     source ~/.bashrc
+     ```
+   - **Windows**:
+     - Search for "Environment Variables" in the Start menu.
+     - Click on "Environment Variables".
+     - Under "System variables", find the `Path` variable and click "Edit".
+     - Add the path to your npm global binaries (you can find this by running `npm bin -g` in your command prompt).
+     - Click OK to save your changes.
+
+4. Verify the installation:
+   ```bash
+   sheno --version
+   ```
+
+---
+
+## Install via Homebrew
+
+If you prefer using Homebrew to manage installations, follow these steps:
+
+### HTTPS (Default)
+
+If you don’t mind entering your GitHub credentials when prompted, you can tap the formula using HTTPS.
+
+1. Tap the formula:
+   ```bash
+   brew tap dev-mahmoud-elshenawy/sheno_cli
+   ```
+
+2. Install the CLI:
+   ```bash
+   brew install sheno_cli
+   ```
+
+3. Use a Personal Access Token (PAT) for authentication if 2FA is enabled on your GitHub account:
+   - Generate a PAT from your GitHub account under **Settings > Developer settings > Personal access tokens**.
+   - Use your GitHub username and PAT as the password when prompted.
+
+### SSH (Recommended)
+
+SSH authentication is recommended as it eliminates the need to enter your username and password each time.
+
+1. Tap the formula using SSH:
+   ```bash
+   brew tap dev-mahmoud-elshenawy/sheno_cli git@github.com:dev-mahmoud-elshenawy/sheno_cli.git
+   ```
+
+2. Install the CLI:
+   ```bash
+   brew install sheno_cli
+   ```
+
+3. Install dependencies and build the project:
+   ```bash
+   npm install && npm run build
+   ```
+
+---
+
+### Verifying Installation
+
+For all installation methods, verify that the CLI is installed correctly by running:
+
+```bash
+sheno --version
+```
+
+---
+
+Enjoy using the **Sheno CLI Tool** to simplify your workflows!

package/.history/INSTALLATION_20250202181656.md

@@ -0,0 +1,118 @@
+# Installation Guide for OptiKit CLI
+
+This guide provides various methods to install the **OptiKit CLI Tool**. Whether you prefer installing via NPM, cloning the repository, or using Homebrew, choose the method that best suits your setup.
+
+---
+
+## Install via NPM
+
+The easiest and most straightforward way to install the **OptiKit CLI** is by using NPM. This method works on all platforms (macOS, Linux, and Windows).
+
+### Steps:
+1. Run the following command to install the CLI globally:
+   ```bash
+   npm install -g sheno_cli
+   ```
+
+2. Verify the installation:
+   ```bash
+   sheno --version
+   ```
+
+---
+
+## Install via Repository Clone
+
+For users who want to work with the source code directly, you can clone the repository and build it locally.
+
+### Steps:
+1. Clone the repository:
+   ```bash
+   git clone https://github.com/dev-mahmoud-elshenawy/sheno_cli.git
+   cd sheno_cli
+   ```
+
+2. Install dependencies and build the project:
+   ```bash
+   npm install && npm run build
+   ```
+
+3. Add the CLI to your PATH (based on your operating system):
+   - **macOS**:
+     ```bash
+     echo 'export PATH="$PATH:/your_path/sheno_cli"' >> ~/.zshrc
+     source ~/.zshrc
+     ```
+   - **Linux**:
+     ```bash
+     echo 'export PATH="$PATH:/your_path/sheno_cli"' >> ~/.bashrc
+     source ~/.bashrc
+     ```
+   - **Windows**:
+     - Search for "Environment Variables" in the Start menu.
+     - Click on "Environment Variables".
+     - Under "System variables", find the `Path` variable and click "Edit".
+     - Add the path to your npm global binaries (you can find this by running `npm bin -g` in your command prompt).
+     - Click OK to save your changes.
+
+4. Verify the installation:
+   ```bash
+   sheno --version
+   ```
+
+---
+
+## Install via Homebrew
+
+If you prefer using Homebrew to manage installations, follow these steps:
+
+### HTTPS (Default)
+
+If you don’t mind entering your GitHub credentials when prompted, you can tap the formula using HTTPS.
+
+1. Tap the formula:
+   ```bash
+   brew tap dev-mahmoud-elshenawy/sheno_cli
+   ```
+
+2. Install the CLI:
+   ```bash
+   brew install sheno_cli
+   ```
+
+3. Use a Personal Access Token (PAT) for authentication if 2FA is enabled on your GitHub account:
+   - Generate a PAT from your GitHub account under **Settings > Developer settings > Personal access tokens**.
+   - Use your GitHub username and PAT as the password when prompted.
+
+### SSH (Recommended)
+
+SSH authentication is recommended as it eliminates the need to enter your username and password each time.
+
+1. Tap the formula using SSH:
+   ```bash
+   brew tap dev-mahmoud-elshenawy/sheno_cli git@github.com:dev-mahmoud-elshenawy/sheno_cli.git
+   ```
+
+2. Install the CLI:
+   ```bash
+   brew install sheno_cli
+   ```
+
+3. Install dependencies and build the project:
+   ```bash
+   npm install && npm run build
+   ```
+
+---
+
+### Verifying Installation
+
+For all installation methods, verify that the CLI is installed correctly by running:
+
+```bash
+sheno --version
+```
+
+---
+
+Enjoy using the **Sheno CLI Tool** to simplify your workflows!