eslint-config-agent 1.0.5

package/.claude/settings.json

@@ -0,0 +1,24 @@
+{
+  "permissions": {
+    "allow": [
+      "Bash(pnpm init:*)",
+      "Bash(pnpm add:*)",
+      "Bash(pnpm validate:*)",
+      "Bash(pnpm lint:*)",
+      "Bash(pnpm eslint:*)",
+      "Bash(cat:*)",
+      "WebSearch",
+      "Bash(pnpm test:*)",
+      "Bash(npm config get:*)",
+      "Bash(pnpm release:patch:*)",
+      "Bash(git add:*)",
+      "Bash(git commit:*)",
+      "Bash(pnpm remove:*)",
+      "Bash(node:*)",
+      "Bash(npx eslint:*)",
+      "Bash(npx @typescript-eslint/parser:*)"
+    ],
+    "deny": [],
+    "ask": []
+  }
+}

package/.env.example

@@ -0,0 +1,5 @@
+# Environment variables for ESLint Config package
+
+# NPM Token for publishing packages
+# Get this from https://www.npmjs.com/settings/tokens
+NPM_TOKEN=your_npm_token_here

package/.release-it.json

@@ -0,0 +1,39 @@
+{
+  "git": {
+    "commit": true,
+    "commitMessage": "Release v${version}",
+    "tag": true,
+    "tagName": "v${version}",
+    "push": true,
+    "requireCleanWorkingDir": true,
+    "requireUpstream": false
+  },
+  "npm": {
+    "publish": true,
+    "publishPath": ".",
+    "access": "public",
+    "token": "${NPM_TOKEN}",
+    "otp": false
+  },
+  "github": {
+    "release": true
+  },
+  "hooks": {
+    "before:init": ["pnpm validate", "pnpm test:ci"],
+    "before:npm:publish": "echo '//registry.npmjs.org/:_authToken=${NPM_TOKEN}' > .npmrc && npm config set access public",
+    "after:npm:publish": "rm -f .npmrc",
+    "after:bump": "echo 'Version bumped to ${version}'"
+  },
+  "plugins": {
+    "@release-it/conventional-changelog": {
+      "preset": "conventionalcommits",
+      "infile": "CHANGELOG.md",
+      "header": "# Changelog\n\nAll notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.\n\n"
+    }
+  },
+  "prompt": {
+    "ghRelease": false,
+    "glRelease": false,
+    "publish": true
+  }
+}

package/CHANGELOG.md

@@ -0,0 +1,45 @@
+# Changelog
+
+All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines.
+
+
+
+## [1.0.5](https://github.com/tupe12334/eslint-config/compare/v1.0.4...v1.0.5) (2025-08-29)
+
+### Features
+
+* enhance documentation with additional commands for release management and testing guidelines ([4cc298d](https://github.com/tupe12334/eslint-config/commit/4cc298d195edfee31dfd3ec2dc2e5343707dae35))
+* update ESLint rules for type assertions and enhance test coverage for invalid usage ([f53b9d6](https://github.com/tupe12334/eslint-config/commit/f53b9d6ca40f949e073d6eb08e70ec6ad0117518))
+* update ESLint rules to disallow optional chaining syntax in member and call expressions ([6b9ab7b](https://github.com/tupe12334/eslint-config/commit/6b9ab7bdae7b8608a19e2f888c72af18382f66da))
+
+## [1.0.4](https://github.com/tupe12334/eslint-config/compare/v1.0.3...v1.0.4) (2025-08-29)
+
+### Features
+
+* add ESLint rules to disallow Record with string literal keys and create corresponding test cases ([98189f2](https://github.com/tupe12334/eslint-config/commit/98189f26ef78a1cf0fc89bcf47848d8761b8a5e9))
+* add tests for new union type rule to validate correct usage and trigger errors ([7936470](https://github.com/tupe12334/eslint-config/commit/7936470d10003dab6353650038e5b02e9e79b657))
+
+## [1.0.3](https://github.com/tupe12334/eslint-config/compare/v1.0.2...v1.0.3) (2025-08-29)
+
+### Features
+
+* add initial ESLint configuration with permissions for various commands ([d7613aa](https://github.com/tupe12334/eslint-config/commit/d7613aa115b04e3aa45e6707dea350f9ec8b1678))
+* add permission for npx @typescript-eslint/parser command in settings ([1b87420](https://github.com/tupe12334/eslint-config/commit/1b87420bddd5fd3894fe34b38a41059b03eb2f5b))
+* add permission for npx eslint command in settings ([77ae39a](https://github.com/tupe12334/eslint-config/commit/77ae39ae84c5d0a186a88acef2cd5aa1e68153bc))
+* enhance TypeScript rules by enforcing no-explicit-any and consistent type assertions ([d2677c6](https://github.com/tupe12334/eslint-config/commit/d2677c6359ea956d36d9e02abcf173131c49f437))
+* remove settings.local.json and add it to .gitignore ([553a861](https://github.com/tupe12334/eslint-config/commit/553a861644ce81689400920892ea7eb64822703d))
+
+## [1.0.2](https://github.com/tupe12334/eslint-config/compare/v1.0.1...v1.0.2) (2025-08-25)
+
+### Features
+
+* enhance ESLint configuration with optional preact plugin and update peer dependencies ([09f63d5](https://github.com/tupe12334/eslint-config/commit/09f63d5249c8c6f6832668b926b5c1b81d6d8144))
+
+## 1.0.1 (2025-08-25)
+
+### Features
+
+* **settings:** add permission for pnpm release command in settings ([3c14b7a](https://github.com/tupe12334/eslint-config/commit/3c14b7a8b2da8461bcee7ba7eeb0811cb9f995d5))
+* **setup:** add environment setup instructions and example file for publishing ([a1342f1](https://github.com/tupe12334/eslint-config/commit/a1342f19849b91b9d2579e0e657e9fe624dac156))
+* **setup:** update NPM token instructions and add hooks for .npmrc management ([e78e9bb](https://github.com/tupe12334/eslint-config/commit/e78e9bb5a6ab5d9e21edd852b33ea6f077623387))
+* **tests:** add comprehensive ESLint configuration test runner ([86ee8d4](https://github.com/tupe12334/eslint-config/commit/86ee8d4a83c7b620bf3909c368ba8f8926726c15))

package/CLAUDE.md

@@ -0,0 +1,93 @@
+# CLAUDE.md
+
+This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
+
+## Project Overview
+
+This is an ESLint configuration package (`eslint-config-agent`) that provides TypeScript and JavaScript linting rules. The package exports a reusable ESLint configuration that can be consumed by other projects.
+
+## Development Setup
+
+The project uses pnpm as the package manager. Dependencies are already installed.
+
+## Common Commands
+
+### Development & Testing
+- `pnpm lint` - Run ESLint on the entire project
+- `pnpm test` - Run comprehensive test suite with categorized validation  
+- `pnpm test:valid` - Test valid code samples
+- `pnpm test:invalid` - Test invalid code samples that should trigger errors
+- `pnpm test:hooks` - Test React hooks rules
+- `pnpm test:imports` - Test import/export patterns  
+- `pnpm test:edge` - Test edge cases and boundary conditions
+- `pnpm test:performance` - Test large files and complex scenarios
+- `pnpm test:ci` - Run ESLint with zero warnings allowed (used for CI)
+- `pnpm validate` - Run legacy configuration validation
+
+### Release Management
+- `pnpm release` - Interactive release process (recommended)
+- `pnpm release:patch` - Patch version release (1.0.0 → 1.0.1)
+- `pnpm release:minor` - Minor version release (1.0.0 → 1.1.0) 
+- `pnpm release:major` - Major version release (1.0.0 → 2.0.0)
+- `pnpm release:dry` - Test release process without publishing
+
+## Architecture
+
+The project follows the modern ESLint flat configuration format:
+
+- `index.js` - Main configuration export that other projects will consume
+- `eslint.config.js` - Local ESLint configuration for this project itself  
+- `test/` - Test files that validate the ESLint rules are working correctly
+- `scripts/validate-config.js` - Validation script that tests the configuration
+
+The main export provides separate configurations for:
+- TypeScript/TSX files with React/Preact support
+- JavaScript/JSX files with React/Preact support  
+- Node.js scripts with appropriate globals
+
+Key features:
+- Disallows optional chaining (`?.`) and nullish coalescing (`??`)
+- Enforces JSX only in `.tsx`/`.jsx` files
+- Limits function length to 100 lines
+- Warns about trailing spaces
+- Supports both React and Preact
+
+## Testing
+
+The package includes extensive testing infrastructure with 12+ test files covering different scenarios:
+
+**Test Categories:**
+- **Valid Code**: Files that should pass with minimal warnings
+- **Invalid Code**: Files that intentionally trigger specific errors  
+- **React Hooks**: Tests for hooks rules (exhaustive-deps, rules-of-hooks)
+- **Import/Export**: Tests for module patterns and import rules
+- **Edge Cases**: Boundary conditions and complex JSX structures
+- **Performance**: Large files and complex components for performance testing
+
+**Test Tools:**
+- `scripts/test-runner.js` - Main test runner with categorized validation and statistics
+- `scripts/validate-config.js` - Legacy validator for basic functionality checks
+
+**Key Rules Tested:**
+- Nullish coalescing operator (`??`) restriction
+- Optional chaining (`?.`) restriction  
+- JSX filename extension enforcement
+- Function length limits
+- Trailing spaces detection
+- React hooks dependency validation
+- Conditional hook usage detection
+- TypeScript type assertion rules (`no-explicit-any`, consistent type assertions)
+- Record type restrictions with string literal keys
+- Union type validation
+
+Run `pnpm test` for comprehensive testing or `pnpm validate` for basic validation.
+
+## Release Process
+
+This package uses `release-it` with automated version management and changelog generation. Before any release:
+
+1. Ensure all tests pass: `pnpm test:ci` and `pnpm validate` 
+2. Working directory must be clean (all changes committed)
+3. Use conventional commit messages for better changelog generation
+
+The release process automatically handles version bumping, changelog generation, git tagging, and npm publishing. See RELEASING.md for detailed instructions.

package/README.md

@@ -0,0 +1,128 @@
+# eslint-config-agent
+
+A comprehensive ESLint configuration package that provides TypeScript, React, and Preact linting rules with strict coding standards.
+
+## Features
+
+- **TypeScript Support**: Full TypeScript ESLint integration
+- **React & Preact**: Complete support for both React and Preact projects
+- **Strict Standards**: Enforces explicit null/undefined checks, disallows optional chaining and nullish coalescing
+- **Code Quality**: Function length limits, trailing space detection, and more
+- **Modern ESLint**: Uses the new flat configuration format
+
+## Installation
+
+```bash
+npm install --save-dev eslint-config-agent
+# or
+pnpm add -D eslint-config-agent
+# or
+yarn add -D eslint-config-agent
+```
+
+## Usage
+
+Create an `eslint.config.js` file in your project root:
+
+```javascript
+import config from 'eslint-config-agent';
+
+export default config;
+```
+
+Or extend it with your own rules:
+
+```javascript
+import baseConfig from 'eslint-config-agent';
+
+export default [
+  ...baseConfig,
+  {
+    rules: {
+      // Your custom rules here
+    },
+  },
+];
+```
+
+## Rules Overview
+
+### Key Restrictions
+- **No Optional Chaining** (`?.`): Use explicit null/undefined checks instead
+- **No Nullish Coalescing** (`??`): Use explicit null/undefined checks instead
+- **JSX File Extensions**: JSX is only allowed in `.tsx` and `.jsx` files
+- **Function Length**: Functions are limited to 100 lines (warnings)
+- **Trailing Spaces**: Not allowed (warnings)
+
+### Disabled Rules
+This configuration disables many common ESLint and React rules to provide a more flexible development experience while maintaining code quality through specific restrictions.
+
+## Development
+
+### Testing
+
+The package includes comprehensive testing to validate the configuration works correctly across various scenarios:
+
+```bash
+# Run comprehensive test suite
+pnpm test
+
+# Run specific test categories
+pnpm test:valid          # Valid code samples
+pnpm test:invalid        # Invalid code samples  
+pnpm test:hooks          # React hooks rules
+pnpm test:imports        # Import/export patterns
+pnpm test:edge           # Edge cases
+pnpm test:performance    # Large files and complex code
+
+# Legacy validation script
+pnpm validate
+
+# Lint the entire project
+pnpm lint
+
+# CI-ready linting (zero warnings allowed)
+pnpm test:ci
+```
+
+### Test Coverage
+
+The test suite covers 8+ categories with detailed validation:
+
+**Core Rules Testing:**
+- `test/valid.tsx` - Valid TypeScript React code
+- `test/invalid.tsx` - Code that should trigger specific errors
+- `test/jsx-extension-test.js` - JSX in JS file testing (should error)
+- `test/long-function.tsx` - Function length limit testing
+
+**Framework-Specific Testing:**
+- `test/preact-test.tsx` - Preact component validation
+- `test/react-hooks-rules.tsx` - React hooks rules validation
+- `test/typescript-rules.ts` - TypeScript-specific features
+
+**Advanced Testing:**
+- `test/import-export-rules.ts` - Import/export patterns
+- `test/edge-cases.tsx` - Edge cases and boundary conditions
+- `test/performance-test.tsx` - Large files and complex scenarios
+
+**Automated Validation:**
+- `scripts/test-runner.js` - Comprehensive test runner with categorized validation
+- `scripts/validate-config.js` - Legacy configuration validator
+
+## Supported File Types
+
+- **TypeScript**: `.ts`, `.tsx`
+- **JavaScript**: `.js`, `.jsx`
+- **Frameworks**: React, Preact
+- **Module Systems**: ES Modules
+
+## Dependencies
+
+- ESLint 9.x
+- TypeScript ESLint
+- React ESLint plugins
+- Preact ESLint plugin
+
+## License
+
+ISC

package/RELEASING.md

@@ -0,0 +1,124 @@
+# Release Guide
+
+This document describes how to release new versions of `@tupe12334/eslint-config`.
+
+## Prerequisites
+
+1. **NPM Access**: Ensure you have publish access to the `@tupe12334/eslint-config` package on npm
+2. **Authentication**: Configure your npm authentication token in `.npmrc`:
+   ```
+   //registry.npmjs.org/:_authToken=your-token-here
+   ```
+3. **Clean Working Directory**: Ensure all changes are committed and your working directory is clean
+
+## Release Process
+
+The project uses `release-it` for automated releases with manual control at each step.
+
+### Interactive Release (Recommended)
+
+```bash
+pnpm release
+```
+
+This will:
+1. Run validation tests (`pnpm validate` and `pnpm test:ci`)
+2. Prompt you to select the version bump (patch, minor, major, or custom)
+3. Generate a changelog based on conventional commits
+4. Create a git tag
+5. Commit the version bump
+6. Push changes to the remote repository
+7. Publish to npm
+
+### Specific Version Releases
+
+For specific version types:
+
+```bash
+# Patch release (1.0.0 → 1.0.1)
+pnpm release:patch
+
+# Minor release (1.0.0 → 1.1.0)
+pnpm release:minor
+
+# Major release (1.0.0 → 2.0.0)
+pnpm release:major
+```
+
+### Dry Run
+
+To test the release process without actually publishing:
+
+```bash
+pnpm release:dry
+```
+
+## Pre-Release Checklist
+
+Before running a release, ensure:
+
+- [ ] All tests pass (`pnpm test:ci`)
+- [ ] Configuration validation passes (`pnpm validate`)
+- [ ] CHANGELOG.md is up to date (will be auto-generated)
+- [ ] Working directory is clean
+- [ ] You're on the correct branch (usually `main`)
+- [ ] All intended changes are committed
+
+## Version Strategy
+
+This package follows [Semantic Versioning (SemVer)](https://semver.org/):
+
+- **Patch** (1.0.x): Bug fixes and backwards-compatible changes
+- **Minor** (1.x.0): New features that are backwards-compatible
+- **Major** (x.0.0): Breaking changes
+
+## Commit Message Format
+
+For better changelog generation, use conventional commit messages:
+
+```
+type(scope): description
+
+Types:
+- feat: New feature
+- fix: Bug fix
+- docs: Documentation changes
+- style: Code style changes
+- refactor: Code refactoring
+- test: Test changes
+- chore: Maintenance tasks
+```
+
+Examples:
+- `feat: add support for new ESLint rule`
+- `fix: resolve TypeScript configuration conflict`
+- `docs: update installation instructions`
+
+## Troubleshooting
+
+### Authentication Issues
+- Ensure your `.npmrc` file contains a valid authentication token
+- Verify you have publish access to the package
+
+### Test Failures
+- All tests must pass before release
+- Run `pnpm validate` and `pnpm test:ci` to identify issues
+
+### Git Issues
+- Ensure your working directory is clean
+- Make sure you're on the correct branch
+- Verify remote repository access
+
+### Publishing Issues
+- Check network connectivity
+- Verify npm registry access
+- Ensure package name is not already taken (for major versions)
+
+## Post-Release
+
+After a successful release:
+
+1. Verify the package is available on [npmjs.com](https://npmjs.com/package/@tupe12334/eslint-config)
+2. Test installation in a separate project
+3. Update any dependent projects that use this configuration
+4. Announce the release if significant changes were made

package/SETUP.md

@@ -0,0 +1,48 @@
+# Setup Instructions
+
+## Environment Setup for Publishing
+
+To publish this package, you need to set up environment variables for authentication:
+
+1. Copy the example environment file:
+   ```bash
+   cp .env.example .env
+   ```
+
+2. Get your NPM authentication token:
+   - Go to https://www.npmjs.com/settings/tokens
+   - Create a new "Automation" token (this bypasses OTP requirements)
+   - Make sure to select "Automation" type, not "Publish" 
+   - Copy the token value
+
+3. Edit the `.env` file and replace `your_npm_token_here` with your actual NPM token:
+   ```bash
+   NPM_TOKEN=npm_xxxxxxxxxxxxxxxxxxxxxxxxxx
+   ```
+
+## Publishing
+
+Once the `.env` file is set up, you can publish using:
+
+```bash
+# Patch release (1.0.0 -> 1.0.1)
+pnpm release:patch
+
+# Minor release (1.0.0 -> 1.1.0)  
+pnpm release:minor
+
+# Major release (1.0.0 -> 2.0.0)
+pnpm release:major
+
+# Dry run to test without publishing
+pnpm release:dry
+```
+
+The release process will:
+1. Run validation tests
+2. Run lint checks with zero warnings
+3. Bump the version number
+4. Generate a changelog
+5. Create a git tag
+6. Publish to NPM
+7. Create a GitHub release

package/eslint.config.js

@@ -0,0 +1,3 @@
+import config from './index.js';
+
+export default config;