Add ESLint configuration for TypeScript

[MiWeiss]

Summary

• Added ESLint with TypeScript support for static code analysis
• Configured sensible rules for browser extension development
• Added lint scripts to package.json

Changes Made

New Dependencies

"eslint": "^8.57.0",
"@typescript-eslint/parser": "^5.62.0",
"@typescript-eslint/eslint-plugin": "^5.62.0"

New Scripts

"lint": "eslint \"src/**/*.{ts,tsx}\"",
"lint:fix": "eslint \"src/**/*.{ts,tsx}\" --fix"

Configuration File (.eslintrc.json)

Extends:

• eslint:recommended - Core ESLint rules
• plugin:@typescript-eslint/recommended - TypeScript-specific rules

Custom Rules:

• @typescript-eslint/no-explicit-any: "warn" - Warn on any types (don't block)
• @typescript-eslint/no-unused-vars: "warn" - Warn on unused vars, allow _ prefix
• no-console: "off" - Allow console statements (common in extensions)

Environment:

• Browser, ES2020, Node.js, WebExtensions APIs

Ignored Patterns:

• dist/, node_modules/, webpack/, .temp/

Why This Matters

Benefits:

1. Catch bugs early - Static analysis finds issues before runtime
2. Consistent style - Enforces team coding standards
3. Better maintainability - Easier to read and understand code
4. IDE integration - Real-time feedback while coding
5. CI/CD ready - Can add linting to workflows

Common Issues Detected:

• Unused variables and imports
• Missing return types
• Unreachable code
• Type mismatches
• Potential null/undefined issues

Usage

Check for linting issues:

npm run lint

Auto-fix issues where possible:

npm run lint:fix

Next Steps

Consider adding:

• Lint step to CI/CD workflows
• Pre-commit hook for automatic linting
• Additional rules based on team preferences

Test Plan

• Run npm install to install new dependencies
• Run npm run lint and verify it checks TypeScript files
• Fix any immediate linting issues found
• Verify npm run lint:fix auto-fixes applicable issues

🤖 Generated with Claude Code