OSS Tanbou
Sign in with GitHub

typescript-eslint

View on GitHubProject website

bring ESLint recommended rules and TypeScript parsing together in a Flat Config setup

OSS scale score 294.3OSS health 100Update pace 90 commits/30d
About these scores

OSS scale score is an unbounded metric that log-compresses and weights Stars, Watchers, Forks, and Contributors. Discovery score is the current OSS scale score minus the score at discovery. Update pace is commits in the last 30 days, growth momentum is the OSS scale score difference within the recent observation window, and OSS health is a 0–100 rating based on available recency, Community Health, and release data.

Stars
16,408
Primary language
TypeScript
License
MIT
Repository last updated
Oct 5, 2026
On this page

Overview

typescript-eslint provides the parser, plugin, and shared configurations that let ESLint analyze TypeScript. The v8.71.0 typescript-eslint package offers one entry point for Flat Config, so JavaScript and TypeScript can share the same lint workflow.

Features and best fit

Based on official documentation; not hands-on tested · Content checked:

Key features

Use the parser, plugin, and shared configs from one package

The typescript-eslint package depends on @typescript-eslint/parser, the ESLint plugin, and TypeScript AST utilities, giving Flat Config a single integration entry point instead of requiring each package to be wired manually.

Sources: [3]

Combine recommended JavaScript and TypeScript configs in Flat Config

The official Quickstart combines the recommended @eslint/js config with tseslint.configs.recommended in eslint.config.mjs, allowing JavaScript and TypeScript files to be checked in the same ESLint run.

Sources: [1]

Opt into rules that use TypeScript type information

Projects that need deeper analysis can move to recommendedTypeChecked with parserOptions.projectService: true. Those rules ask TypeScript for project type information, which is more powerful but slower than syntax-only linting.

Sources: [2]

Best fit

Fits TypeScript frontends that want one standardized lint workflow

It is useful in React, Vue, and other TypeScript frontends that want to keep ESLint as the common runner while adding rules aware of TypeScript syntax and types. Framework-specific rules remain separate plugins.

Sources: [1][3]

Before adoption

v8.71.0 does not include TypeScript 7 in its peer range

typescript-eslint v8.71.0 declares TypeScript >=4.8.4 <6.1.0 and ESLint ^8.57.0 || ^9.0.0 || ^10.0.0 as peer dependencies. Projects already on TypeScript 7 should verify a compatible typescript-eslint release instead of adopting this version unchanged.

Sources: [3]

Check the Node.js range and the cost of typed linting

Version 8.71.0 requires Node.js ^18.18.0 || ^20.9.0 || >=21.1.0. Typed linting also analyzes the TypeScript project, so its CI and editor cost should be evaluated separately from syntax-only rules.

Sources: [3][2]

Official sources

  1. [1]typescript-eslint v8.71.0 Quickstart(2026-10-05)
  2. [2]typescript-eslint v8.71.0 Typed Linting guide(2026-10-05)
  3. [3]typescript-eslint v8.71.0 package metadata(2026-10-05)
  4. [4]typescript-eslint v8.71.0 release(2026-10-05)
  5. [5]typescript-eslint MIT license(2026-10-05)
Supplemental curator note

TypeScript 7 is outside the peer-dependency range of v8.71.0. Projects on TypeScript 7 should verify a compatible typescript-eslint release instead of pinning this version. Type-aware linting also analyzes the project, so measure its CI cost separately.

Try it in 3 steps

  1. 1

    Install typescript-eslint v8.71.0 with compatible ESLint and TypeScript versions

    Create an isolated project with the packages from the official Quickstart pinned inside the peer-dependency range of v8.71.0.

    demo=$(mktemp -d "${TMPDIR:-/tmp}/typescript-eslint.XXXXXX") && cd "$demo" && npm init -y >/dev/null && npm install --save-exact --save-dev eslint@10.10.0 @eslint/js@10.10.0 typescript@5.9.2 typescript-eslint@8.71.0
  2. 2

    Create a Flat Config and a small TypeScript file

    Use a minimal form of the recommended Flat Config so JavaScript and TypeScript can share the same lint run.

    printf "%s\n" "import js from '@eslint/js';" "import { defineConfig } from 'eslint/config';" "import tseslint from 'typescript-eslint';" "export default defineConfig({ files: ['**/*.{js,ts}'], extends: [js.configs.recommended, tseslint.configs.recommended] });" > eslint.config.mjs && printf "%s\n" "const answer: number = 42;" "console.log(answer);" > example.ts
  3. 3

    Lint the TypeScript file with ESLint

    Run the same ESLint CLI flow as the official guide and confirm that the TypeScript file is parsed and checked.

    npx eslint example.ts
Check the official README

Growth

Growth trends · Last 30 days

16,408 Stars

Trend data is still being collected.

Development activity

Last 90 days · weekly

Commits (last 30 days)
90
Open PRs
37

Development activity is still being collected.

Built with

Categories and tags

Categories

Tags

GitHub data

GitHub dataView detailed GitHub data
View on GitHub

GitHub Topics

  • typescript
  • eslint
  • eslint-plugin
  • tslint
  • eslintplugin
  • plugin
Stars
16,408
Forks
3,028
Watchers
92
Open issues
177
Contributors
442
Owner type
Organization
Primary language
TypeScript
License
MIT
Repository last updated
Oct 5, 2026
Write a related article

Share a guide or use case for this OSS in Markdown. Articles are published after administrator approval.

Report incorrect information

Tell us if any listing information is incorrect or outdated.

After reading this page, do you know what to do next?