Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

WARNING: You are running a version of TypeScript that typescript-estree does not support

ErrorWARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree

Short answer

The parser logs this warning when your TypeScript version is outside the range typescript-eslint supports. It is only a warning by default, and linting still runs. Check the supported range, then upgrade typescript-eslint or move TypeScript into range. As a last step, set onUnsupportedTypeScriptVersion to ignore.

  • Applies to typescript-eslint 8, TypeScript 5, Node.js 22
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Print the TypeScript and typescript-eslint versions that are installed, and compare TypeScript with the supported range.

    npm ls typescript typescript-eslint @typescript-eslint/parser
  2. 2Match what you see, then jump to its fix

    1. 1You recently upgraded typescript, and the warning started then.TypeScript is newer than the installed typescript-eslint supportsFix
    2. 2npm ls shows a version with -beta or -rc in its name.TypeScript is a beta or release candidateFix
    3. 3Linting works and the team has chosen to stay on this TypeScript version.You accept the version and only want a quiet logFix

What does the error look like?

  • WARNING: You are currently running a version of TypeScript which is not officially supported by @typescript-eslint/typescript-estree

Cause 1 of 3

TypeScript is newer than the installed typescript-eslint supports

1Check

typescript-eslint supports TypeScript from 4.8.4 up to, but not including, 6.1.0. Anything above that range gets the warning until typescript-eslint is updated.

npm ls typescript

2Fix

Update typescript-eslint, and if the warning stays, move TypeScript back into the supported range.

npm install --save-dev typescript-eslint@latest
# or, if the project needs it
npm install --save-dev typescript@5

3Verify

Run ESLint and check that the warning is gone.

npx eslint .

Confirmed by typescript-eslint.io

Did this fix it?

Cause 2 of 3

TypeScript is a beta or release candidate

1Check

Beta releases are not supported, and release candidates generally are not either.

npx tsc --version

2Fix

Install a stable TypeScript release.

npm install --save-dev typescript@latest

3Verify

Run ESLint again.

npx eslint .

Confirmed by typescript-eslint.io

Did this fix it?

Cause 3 of 3

You accept the version and only want a quiet log

1Check

The warning is the default, and the option onUnsupportedTypeScriptVersion decides what happens. warn logs, error throws, ignore stays silent.

grep -n "onUnsupportedTypeScriptVersion" eslint.config.* .eslintrc.*

2Fix

Set the option to ignore. Use error in CI if you want unsupported versions to fail the run.

languageOptions: {
  parserOptions: {
    onUnsupportedTypeScriptVersion: 'ignore',
  },
},

3Verify

Run ESLint and check that no warning prints.

npx eslint .

Confirmed by typescript-eslint.io

Did this fix it?

How do I stop it coming back?

  • Upgrade typescript and typescript-eslint in the same commit.
  • Pin typescript to a minor version so a plain install does not move it out of range.
  • Do not report lint bugs against a TypeScript version outside the supported range.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Web apps

tsconfig rejects allowImportingTsExtensions

An error that allowImportingTsExtensions needs noEmit or emitDeclarationOnly

allowImportingTsExtensions lets files import each other with .ts or .tsx extensions, and TypeScript only allows it together with noEmit or emitDeclarationOnly.

2 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.