How to fix Invalid TypeScript version for @typescript-eslint rule in TypeScript

What this error means

The "Invalid TypeScript version" or "You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree" warning occurs when there's a version mismatch between TypeScript and the typescript-eslint tooling. typescript-eslint mirrors DefinitelyTyped's support window, meaning it only officially supports TypeScript versions less than 2 years old. The warning appears during ESLint execution and indicates that while your code may work fine, the typescript-eslint team doesn't guarantee compatibility and won't accept bug reports for unsupported version combinations. This commonly happens when: 1. **Using an older TypeScript version**: Your project uses TypeScript 4.7 or earlier while typescript-eslint has moved on 2. **Using a bleeding-edge TypeScript version**: You've upgraded to a brand new TypeScript release before typescript-eslint has added official support 3. **Dependency version drift**: Different parts of your toolchain have updated independently, creating mismatches Currently, typescript-eslint supports TypeScript versions >=4.8.4 <6.0.0. The project actively maintains support for the latest stable TypeScript releases, typically adding support within days of a new TypeScript version being released.

Typical symptoms

• Console warning: 'WARNING: You are currently running a version of TypeScript which is not officially supported'
• ESLint runs but displays version compatibility warnings in terminal output
• IDE shows warnings about TypeScript version compatibility with ESLint
• CI/CD pipelines display typescript-eslint version warnings but still pass
• Warning mentions @typescript-eslint/typescript-estree package specifically
• ESLint rules work correctly despite the warning message

Common causes

1. TypeScript version is below 4.8.4 (too old for current typescript-eslint)
2. TypeScript version is 6.0 or higher (newer than typescript-eslint supports)
3. typescript-eslint packages are outdated while TypeScript has been upgraded
4. TypeScript was upgraded to latest version before typescript-eslint added support
5. Mismatched versions between @typescript-eslint/parser and @typescript-eslint/eslint-plugin
6. Node.js version incompatibility affecting package resolution

How to fix "Invalid TypeScript version for @typescript-eslint rule"

# Check TypeScript version
npx tsc --version

# Check typescript-eslint versions
npm list typescript @typescript-eslint/parser @typescript-eslint/eslint-plugin

# Or check package.json directly
cat package.json | grep -E "typescript|@typescript-eslint"

# Update both packages together to ensure version compatibility
npm install --save-dev @typescript-eslint/parser@latest @typescript-eslint/eslint-plugin@latest

# Or using yarn
yarn upgrade @typescript-eslint/parser @typescript-eslint/eslint-plugin --latest

# Or using pnpm
pnpm update @typescript-eslint/parser @typescript-eslint/eslint-plugin --latest

// package.json - ensure versions match
{
  "devDependencies": {
    "@typescript-eslint/eslint-plugin": "^8.46.4",
    "@typescript-eslint/parser": "^8.46.4"
  }
}

npx eslint .

# Update to latest TypeScript 5.x
npm install --save-dev typescript@latest

# Or install a specific version
npm install --save-dev typescript@5.6.2

# For yarn
yarn upgrade typescript@latest

# For pnpm
pnpm update typescript@latest

# Clear TypeScript build cache
rm -rf dist/ build/ .tsbuildinfo

# Recompile to check for new errors
npx tsc --noEmit

# Restart TypeScript server in VS Code
# Press Cmd/Ctrl + Shift + P → "TypeScript: Restart TS Server"

# List all TypeScript-related packages
npm list typescript @types/node ts-node tsx @typescript-eslint/parser @typescript-eslint/eslint-plugin

# Update all together
npm install --save-dev \
  typescript@latest \
  @typescript-eslint/parser@latest \
  @typescript-eslint/eslint-plugin@latest \
  @types/node@latest

# Update in root
npm install --save-dev --workspaces \
  typescript@latest \
  @typescript-eslint/parser@latest \
  @typescript-eslint/eslint-plugin@latest

# Or use syncpack to sync versions across workspace packages
npx syncpack fix-mismatches

// package.json
{
  "devDependencies": {
    "typescript": "^5.6.2",
    "@typescript-eslint/eslint-plugin": "^8.46.4",
    "@typescript-eslint/parser": "^8.46.4",
    "eslint": "^9.0.0"
  }
}

module.exports = {
  parser: "@typescript-eslint/parser",
  parserOptions: {
    ecmaVersion: "latest",
    sourceType: "module",
    project: "./tsconfig.json",
    warnOnUnsupportedTypeScriptVersion: false, // Disable warning
  },
  plugins: ["@typescript-eslint"],
  extends: [
    "eslint:recommended",
    "plugin:@typescript-eslint/recommended",
  ],
};

{
  "parser": "@typescript-eslint/parser",
  "parserOptions": {
    "ecmaVersion": "latest",
    "sourceType": "module",
    "project": "./tsconfig.json",
    "warnOnUnsupportedTypeScriptVersion": false
  },
  "plugins": ["@typescript-eslint"],
  "extends": [
    "eslint:recommended",
    "plugin:@typescript-eslint/recommended"
  ]
}

# Remove all dependencies and cache
rm -rf node_modules
rm package-lock.json  # or yarn.lock / pnpm-lock.yaml

# Clear npm cache
npm cache clean --force

# Reinstall with exact versions
npm install

# Verify no duplicate TypeScript installations
npm ls typescript
# Should show a single version, not multiple

# Check global TypeScript
npm list -g typescript

# If global TypeScript exists and causes issues, uninstall
npm uninstall -g typescript

# Always use project-local TypeScript
npx tsc --version

npx eslint --version
npx eslint . --debug 2>&1 | grep -i typescript

Advanced notes

# Install TypeScript nightly or beta
npm install --save-dev typescript@next

# Or specific beta
npm install --save-dev typescript@5.7.0-beta

// .eslintrc.js
module.exports = {
  parserOptions: {
    warnOnUnsupportedTypeScriptVersion: false,
  },
};

// package.json (root)
{
  "devDependencies": {
    "typescript": "^5.6.2",
    "@typescript-eslint/parser": "^8.46.4",
    "@typescript-eslint/eslint-plugin": "^8.46.4"
  },
  "workspaces": ["packages/*"]
}

npm ls typescript --all

# pnpm-workspace.yaml
packages:
  - 'packages/*'

# .npmrc
shamefully-hoist=true  # Helps avoid version conflicts

# Sync all package versions
npx lerna exec -- npm install typescript@latest @typescript-eslint/parser@latest @typescript-eslint/eslint-plugin@latest

// package.json - use exact versions in CI
{
  "devDependencies": {
    "typescript": "5.6.2",           // No caret ^
    "@typescript-eslint/parser": "8.46.4",
    "@typescript-eslint/eslint-plugin": "8.46.4"
  }
}

# In CI, use exact locked versions
npm ci  # Not npm install

# Debug ESLint execution
DEBUG=eslint:* npx eslint .

# Or typescript-eslint specific debug
TSESTREE_SINGLE_RUN=true npx eslint .

# Check TypeScript compiler API version
node -e "console.log(require('typescript').version)"

# Find all TypeScript installations
find node_modules -name "typescript" -type d

# Check which version ESLint uses
npx eslint --print-config . | grep -A 10 parserOptions

{
  "overrides": {
    "typescript": "5.6.2"
  }
}

Frequently asked questions

What does "Invalid TypeScript version for @typescript-eslint rule" mean?

The "Invalid TypeScript version" or "You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree" warning occurs when there's a version mismatch between TypeScript and the typescript-eslint tooling. typescript-eslint mirrors DefinitelyTyped's support window, meaning it only officially supports TypeScript versions less than 2 years old. The warning appears during ESLint execution and indicates that while your code may work fine, the typescript-eslint team doesn't guarantee compatibility and won't accept bug reports for unsupported version combinations.

How do I fix "Invalid TypeScript version for @typescript-eslint rule"?

This warning appears when you're using a version of TypeScript that isn't officially supported by typescript-eslint. The fix typically involves updating either TypeScript or typescript-eslint to compatible versions, or suppressing the warning if your setup works correctly.

What causes "Invalid TypeScript version for @typescript-eslint rule"?

TypeScript version is below 4.8.4 (too old for current typescript-eslint) TypeScript version is 6.0 or higher (newer than typescript-eslint supports) typescript-eslint packages are outdated while TypeScript has been upgraded

Is the "Invalid TypeScript version for @typescript-eslint rule" error serious?

It is a medium-severity error — more of a blocker than a risk. The steps above resolve it.

Related errors

• @typescript-eslint cannot parse file without TypeScript

  @typescript-eslint cannot parse file without TypeScript

  MEDIUM

• Enum member name must be followed by ',' ':' or '}'

  Enum member name must be followed by ',' ':' or '}'

  MEDIUM

• @typescript-eslint parser requires TypeScript service

  @typescript-eslint parser requires TypeScript service

  MEDIUM

• Enum member must have initializer

  Enum member must have initializer

  MEDIUM

• Cannot find name 'process'. Do you need to install type definitions for node? Try `npm i --save-dev @types/node` and then add 'node' to the types field in your tsconfig.

  How to fix "Cannot find name 'process'" in TypeScript

  MEDIUM

• Module has no exported member 'X'

  How to fix 'Module has no exported member X' error in TypeScript

  MEDIUM

Official resources & further reading

• 📚TypeScript Official Documentation
• 📖
  typescript-eslint - Dependency Versions(Official Docs)
• 📖
  typescript-eslint - Parser Documentation(Official Docs)
• 🐙
  GitHub Issue #7087 - Unsupported TypeScript Version Warning(GitHub)
• 🐙
  ESLint GitHub Issue #18825 - TypeScript Version Warning(GitHub)
• 📖
  typescript-eslint - Troubleshooting FAQs(Official Docs)
• typescript-eslint - Release Notes
• XJavaScript - ESLint Supported TypeScript Versions Guide
• 📖
  typescript-eslint - Release Information(Official Docs)