fix: resolve TypeScript resolver issues and update dependencies

- Fixed "Resolve error: typescript with invalid interface loaded as resolver" by adding `eslint-import-resolver-typescript` as a dependency.
- Properly configured TypeScript resolver in both traditional and flat configurations.
- Updated version to 3.0.3 and documented changes in CHANGELOG.md.

Author: marsicdev

CHANGELOG.md

@@ -2,6 +2,14 @@
 
 All notable changes to this project will be documented in this file.
 
+## [3.0.3] - 2025-07-28
+
+### 🐛 Fixed
+
+- 🔧 Fixed "Resolve error: typescript with invalid interface loaded as resolver" error by adding `eslint-import-resolver-typescript` as a dependency
+- ⚙️ TypeScript resolver is now properly configured in both traditional and flat configurations
+- 📦 Eliminates the need for projects to manually install and configure the TypeScript resolver
+
 ## [3.0.2] - 2025-07-24
 
 ### 💅 Changed

eslint.config.mjs

@@ -99,6 +99,15 @@ const eslintConfig = [
       react: {
         version: "detect",
       },
+      "import/resolver": {
+        typescript: {
+          alwaysTryTypes: true,
+        },
+        node: true,
+      },
+      "import/parsers": {
+        "@typescript-eslint/parser": [".ts", ".tsx"],
+      },
     },
   },
 ];

examples/nextjs14-v3-flat-config/README.md

@@ -9,49 +9,52 @@ While Next.js 14 was designed to work with ESLint 8.x and traditional configurat
 ## Setup
 
 1. Install dependencies:
+
 ```bash
 npm install --save-dev @hypetech/eslint-config@^3.0.0 eslint@^9.0.0 prettier@^3.0.0
 ```
 
 2. Create `eslint.config.mjs` in your project root:
+
 ```js
-import hypetechConfig from '@hypetech/eslint-config';
+import hypetechConfig from '@hypetech/eslint-config'
 
 export default [
-  ...hypetechConfig,
-  {
-    // Add any project-specific overrides here
-    rules: {
-      'no-console': 'warn',
+    ...hypetechConfig,
+    {
+        // Add any project-specific overrides here
+        rules: {
+            'no-console': 'warn',
+        },
     },
-  },
-];
+]
 ```
 
 3. Update your `package.json` scripts:
+
 ```json
 {
-  "scripts": {
-    "lint": "eslint .",
-    "lint:fix": "eslint . --fix"
-  }
+    "scripts": {
+        "lint": "eslint .",
+        "lint:fix": "eslint . --fix"
+    }
 }
 ```
 
 ## Important Notes
 
-- Next.js 14's built-in ESLint integration (`next lint`) expects traditional config format
-- Use `npx eslint` directly instead of `next lint` when using flat config
-- The flat config provides the same rules and functionality as the legacy config
-- You may need to disable Next.js's built-in linting in `next.config.js`:
+-   Next.js 14's built-in ESLint integration (`next lint`) expects traditional config format
+-   Use `npx eslint` directly instead of `next lint` when using flat config
+-   The flat config provides the same rules and functionality as the legacy config
+-   You may need to disable Next.js's built-in linting in `next.config.js`:
 
 ```js
 module.exports = {
-  eslint: {
-    // This allows production builds to complete even if there are ESLint errors
-    ignoreDuringBuilds: true,
-  },
-};
+    eslint: {
+        // This allows production builds to complete even if there are ESLint errors
+        ignoreDuringBuilds: true,
+    },
+}
 ```
 
 ## Migration from Legacy Config
@@ -64,56 +67,61 @@ If you're migrating from the legacy configuration:
 
 ## Benefits of Using Flat Config
 
-- Future-proof your project for ESLint 9.x ecosystem
-- Simpler configuration with better composability
-- Better performance with ESLint 9.x
-- Consistent with modern JavaScript tooling
+-   Future-proof your project for ESLint 9.x ecosystem
+-   Simpler configuration with better composability
+-   Better performance with ESLint 9.x
+-   Consistent with modern JavaScript tooling
 
 ## Example Configuration with Custom Rules
 
 ```js
-import hypetechConfig from '@hypetech/eslint-config';
-import reactPlugin from 'eslint-plugin-react';
+import hypetechConfig from '@hypetech/eslint-config'
+import reactPlugin from 'eslint-plugin-react'
 
 export default [
-  ...hypetechConfig,
-  {
-    files: ['**/*.{js,jsx,ts,tsx}'],
-    plugins: {
-      react: reactPlugin,
+    ...hypetechConfig,
+    {
+        files: ['**/*.{js,jsx,ts,tsx}'],
+        plugins: {
+            react: reactPlugin,
+        },
+        settings: {
+            react: {
+                version: 'detect',
+            },
+        },
+        rules: {
+            'no-console': ['warn', { allow: ['warn', 'error'] }],
+            '@typescript-eslint/no-unused-vars': [
+                'error',
+                {
+                    argsIgnorePattern: '^_',
+                    varsIgnorePattern: '^_',
+                },
+            ],
+        },
     },
-    settings: {
-      react: {
-        version: 'detect',
-      },
+    {
+        // Ignore specific files or directories
+        ignores: ['**/dist/**', '**/build/**', '.next/**'],
     },
-    rules: {
-      'no-console': ['warn', { allow: ['warn', 'error'] }],
-      '@typescript-eslint/no-unused-vars': ['error', { 
-        argsIgnorePattern: '^_',
-        varsIgnorePattern: '^_',
-      }],
-    },
-  },
-  {
-    // Ignore specific files or directories
-    ignores: ['**/dist/**', '**/build/**', '.next/**'],
-  },
-];
+]
 ```
 
 ## Troubleshooting
 
 ### VSCode Integration
 
 Make sure your VSCode is using the workspace version of ESLint:
+
 1. Open Command Palette (Cmd/Ctrl + Shift + P)
 2. Run "ESLint: Select Node Path"
 3. Choose "Use Workspace Version"
 
 ### Type Errors
 
 If you encounter type errors with TypeScript, ensure you have the latest versions:
+
 ```bash
 npm install --save-dev @typescript-eslint/parser@latest @typescript-eslint/eslint-plugin@latest
-```
+```