Release version 0.3.94

### Changes since v0.3.93

Author: Tom Softreck

.eslintrc.js

@@ -3,11 +3,14 @@ module.exports = {
         node: true,
         es6: true
     },
-    extends: 'eslint:recommended',
+    extends: ['eslint:recommended'],
     parserOptions: {
-        ecmaVersion: 2020
+        ecmaVersion: 2022,
+        sourceType: 'module'
     },
     rules: {
-        // Add any specific rules here
+        // Add your specific rules here
+        'no-unused-vars': 'warn',
+        'no-console': 'off'
     }
 };

PUBLISH.md

@@ -235,3 +235,78 @@ npm init
 
 Occasionally, npm registry might have issues. Check [npm status](https://status.npmjs.org/) to ensure the service is operational.
 
+
+
+
+I see the issue – your script is getting caught in an infinite loop because the `version` script in package.json is calling `version.sh`, which then triggers the npm version command, which in turn calls the `version` script again, creating an endless cycle.
+
+Let's fix the `version.sh` script to prevent this infinite loop:
+
+
+
+I've fixed the infinite loop issue in your versioning script. There are two main problems that were causing this:
+
+## 1. Script Infinite Loop Issue
+
+The infinite loop was occurring because:
+
+1. Your package.json had a `"version": "bash version.sh"` script
+2. When you ran `npm version` or the script itself called `npm version`, it triggered this script
+3. Which in turn ran `version.sh` again, creating an endless loop
+
+## 2. Solutions Implemented
+
+I've made two important changes to fix this:
+
+### A. Updated version.sh Script:
+
+1. **Added detection for npm lifecycle events**:
+   ```bash
+   # Detect if being run from npm script to prevent infinite loop
+   if [ "$npm_lifecycle_event" = "version" ]; then
+       echo "Running from npm version hook - skipping automatic versioning"
+       exit 0
+   fi
+   ```
+
+2. **Changed how the version is updated in package.json**:
+   - Instead of using `npm version` which triggers hooks, it directly modifies package.json with Node.js
+   - This avoids the npm lifecycle hooks that were causing the infinite loop
+
+3. **Added better error handling for git commands**:
+   - The script now continues even if git push fails
+   - It properly handles the case where package-lock.json is ignored by git
+
+### B. Updated package.json:
+
+1. **Removed the problematic `version` script**:
+   - This was the main cause of the infinite loop
+
+2. **Added better alternatives**:
+   ```json
+   "increment": "bash version.sh",
+   "publish-npm": "bash version.sh --no-publish && npm publish --access=public",
+   "release:patch": "bash version.sh --patch",
+   "release:minor": "bash version.sh --minor", 
+   "release:major": "bash version.sh --major",
+   "release": "bash version.sh"
+   ```
+
+## How to Use the Fixed Scripts
+
+Now you can use the scripts without fear of infinite loops:
+
+```bash
+# Increment version and publish (interactive)
+./version.sh
+
+# Increment patch version and publish
+npm run release:patch
+
+# Increment version without publishing
+npm run increment -- --no-publish
+
+# Custom version
+./version.sh --version=1.0.0
+```
+

README.md

@@ -7,26 +7,92 @@ ReactStream is a comprehensive CLI toolkit designed to streamline React componen
 1. **Component Analysis**: Analyze React components for common issues, best practices, and optimization opportunities.
 2. **Development Server**: Quickly test and debug React components in isolation without needing to set up a full project.
 
-## Installation
+# ReactStream Installation Guide
+
+## Prerequisites
+
+- Node.js >= 14.0.0
+- npm or yarn
+
+## Option 1: Install from npm
+
+The easiest way to install ReactStream is via npm:
 
 ```bash
-# Install globally from npm
-npm install -g  @reactstream/cli
+# Install globally
+npm install -g @reactstream/cli
+
+# Or install in your project
+npm install --save-dev @reactstream/cli
 ```
 
+## Option 2: Install from Source
+
+If you want to install from source code:
+
+1. Clone the repository:
+   ```bash
+   git clone https://github.com/reactstream/cli.git
+   cd cli
+   ```
+
+2. Install dependencies:
+   ```bash
+   npm install
+   ```
+
+3. Link the package to make the commands available globally:
+   ```bash
+   npm link
+   ```
+
+## Verifying Installation
+
+To verify that ReactStream was installed correctly:
+
 ```bash
-# Or install in your project
-npm install --save-dev  @reactstream/cli
+# Check the version
+reactstream --version
+
+# View help information
+reactstream help
 ```
 
+## Setting Up File Permissions
+
+If you're installing from source, you might need to make the scripts executable:
+
 ```bash
-# Or clone the repository
-git clone https://github.com/reactstream/cli
-cd reactstream
-npm install
-npm link # (to make commands available globally)
+chmod +x bin/reactstream.js
+chmod +x bin/reactstream-analyze.js
 ```
 
+## Troubleshooting
+
+### Common Issues
+
+1. **Command not found**
+
+   If you get a "command not found" error, make sure the npm bin directory is in your PATH:
+   ```bash
+   export PATH="$PATH:$(npm bin -g)"
+   ```
+
+2. **Permission issues**
+
+   If you encounter permission issues when installing globally, you can:
+   ```bash
+   # Option 1: Use sudo (not recommended)
+   sudo npm install -g @reactstream/cli
+   
+   # Option 2: Fix npm permissions (recommended)
+   # See: https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally
+   ```
+
+3. **ESLint errors**
+
+   If you see ESLint errors, make sure you have a valid `.eslintrc.js` file in your project root.
+4. 
 ## Commands
 
 ReactStream now provides a unified command interface with subcommands:

STRUCTURE.md

@@ -0,0 +1,43 @@
+# ReactStream Project Structure
+
+Here's the complete project structure with all required files:
+
+```
+reactstream/
+├── index.js                  # Main entry point
+├── src/                      # Source files
+│   └── reactstream.js        # Core implementation
+├── commands/                 # Command implementations
+│   ├── analyze.js            # Analysis command
+│   └── serve.js              # Development server command
+├── bin/                      # Binary executables
+│   ├── reactstream.js        # Main binary 
+│   └── reactstream-analyze.js # Analyzer binary
+├── package.json              # Project metadata and dependencies
+├── .eslintrc.js              # ESLint configuration
+├── README.md                 # Documentation
+└── DOCS.md                   # Detailed documentation
+```
+
+## Key Files Overview
+
+### 1. index.js
+The main entry point that loads src/reactstream.js.
+
+### 2. src/reactstream.js
+Central implementation file that handles command routing.
+
+### 3. commands/analyze.js
+The React component analyzer implementation.
+
+### 4. commands/serve.js
+The development server implementation.
+
+### 5. bin/reactstream.js
+Executable script for the main command.
+
+### 6. bin/reactstream-analyze.js
+Executable script for the analyze command.
+
+### 7. package.json
+Project configuration with all necessary dependencies and scripts.

UPGRADE.md

@@ -0,0 +1,89 @@
+# upgrade
+
+To upgrade the dependencies in your package.json to the latest versions, you have several options. Here's a systematic approach:
+
+## 1. Using npm outdated and npm update
+
+```bash
+# Check which packages are outdated
+npm outdated
+
+# Update packages within the version range in package.json
+npm update
+
+# Update to the latest versions (including major versions)
+npm update --latest
+```
+
+## 2. Using npm-check-updates (recommended)
+
+This tool specializes in updating package.json dependencies to the latest versions:
+
+```bash
+# Install npm-check-updates
+npm install -g npm-check-updates
+
+# Check for updates without modifying package.json
+ncu
+
+# Update all dependencies in package.json to the latest versions
+ncu -u
+
+# Then install the updated packages
+npm install
+```
+
+## 3. Selective updates
+
+If you want more control, you can update specific packages:
+
+```bash
+# Update a specific package to latest
+npm install package-name@latest
+
+# Update multiple specific packages
+npm install package1@latest package2@latest
+```
+
+## 4. Using the upgrade.sh script
+
+You already have an `upgrade.sh` script that we created earlier. You can run it for an interactive upgrade process:
+
+```bash
+./upgrade.sh
+```
+
+## 5. Safe upgrading strategy
+
+For a production project, consider this safer approach:
+
+1. Create a git branch for the upgrade
+   ```bash
+   git checkout -b dependency-upgrade
+   ```
+
+2. Update dependencies in batches by type
+   ```bash
+   # Update development dependencies first
+   ncu -u -f "/eslint|babel|webpack/"
+   npm install
+   
+   # Update utility libraries
+   ncu -u -f "/chalk|minimist|uuid/"
+   npm install
+   
+   # Update React-related packages
+   ncu -u -f "/react|jsx/"
+   npm install
+   ```
+
+3. Run tests after each batch
+   ```bash
+   npm test
+   ```
+
+4. Commit working changes
+   ```bash
+   git commit -am "Update dependencies: [category]"
+   ```
+

bin/reactstream-analyze.js

@@ -2,4 +2,8 @@
 // bin/reactstream-analyze.js
 
 // This script allows direct execution of the analyze command as a standalone binary
-require('../index.js')(['analyze'].concat(process.argv.slice(2)));
+const minimist = require('minimist');
+const argv = minimist(process.argv.slice(2));
+
+// Prepend the 'analyze' command and pass to the main CLI
+require('../commands/analyze')(argv);