Skip to main content

Linting with Type Information

Some typescript-eslint rules utilize the awesome power of TypeScript's type checking APIs to provide much deeper insights into your code. To tap into TypeScript's additional powers, there are two small changes you need to make to your config file:

  1. Add TypeChecked to the name of any preset configs you're using, namely recommended, strict, and stylistic.
  2. Add languageOptions.parserOptions to tell our parser how to find the TSConfig for each source file.
eslint.config.js
export default tseslint.config(
  eslint.configs.recommended,
  ...tseslint.configs.recommended,
  ...tseslint.configs.recommendedTypeChecked,
  {
    languageOptions: {
      parserOptions: {
        project: true,
        tsconfigRootDir: import.meta.dirname,
      },
    },
  },
);
note

import.meta.dirname is only present for ESM files in Node.js >=20.11.0 / >= 21.2.0.
For CommonJS modules and/or older versions of Node.js, use __dirname or an alternative.

In more detail:

  • tseslint.configs.recommendedTypeChecked is another shared configuration we provide. This one contains recommended rules that additionally require type information.
  • parserOptions.project: true indicates to find the closest tsconfig.json for each source file (see Parser#project).
  • parserOptions.tsconfigRootDir tells our parser the absolute path of your project's root directory (see Parser#tsconfigRootDir).
caution

Your ESLint config file may start receiving a parsing error about type information. See our TSConfig inclusion FAQ.

With that done, run the same lint command you ran before. You may see new rules reporting errors based on type information!

Shared Configurations​

If you enabled the strict shared config and/or stylistic shared config in a previous step, be sure to replace them with strictTypeChecked and stylisticTypeChecked respectively to add their type-checked rules.

eslint.config.js
export default tseslint.config(
  eslint.configs.recommended,
  ...tseslint.configs.strict,
  ...tseslint.configs.stylistic,
  ...tseslint.configs.strictTypeChecked,
  ...tseslint.configs.stylisticTypeChecked,
  // ...
);

You can read more about the rules provided by typescript-eslint in our rules docs and shared configurations docs.

FAQs​

Can I customize the TSConfig used for typed linting?​

The project option can be turned on with either:

  • true: to always use tsconfig.jsons nearest to source files
  • string | string[]: any number of glob paths to match TSConfig files relative to parserOptions.tsconfigRootDir, or the current working directory if that is not provided

For example, if you use a specific tsconfig.eslint.json for linting, you'd specify:

eslint.config.js
export default tseslint.config({
  // ...
  languageOptions: {
    parserOptions: {
      project: './tsconfig.eslint.json',
      tsconfigRootDir: import.meta.dirname,
    },
  },
  // ...
});

See the @typescript-eslint/parser docs for more details.

note

If your project is a multi-package monorepo, see our docs on configuring a monorepo.

How can I disable type-aware linting for a subset of files?​

You can combine ESLint's overrides config in conjunction with our disable-type-checked config to turn off type-aware linting on specific subsets of files.

eslint.config.js
export default tseslint.config(
  eslint.configs.recommended,
  ...tseslint.configs.recommendedTypeChecked,
  ...tseslint.configs.stylisticTypeChecked,
  {
    languageOptions: {
      parserOptions: {
        project: true,
      },
    },
  },
  {
    files: ['**/*.js'],
    ...tseslint.configs.disableTypeChecked,
  },
);
info

If you use type-aware rules from other plugins, you will need to manually disable these rules or use a premade config they provide to disable them.

How is performance?​

Typed rules come with a catch. By including parserOptions.project in your config, you incur the performance penalty of asking TypeScript to do a build of your project before ESLint can do its linting. For small projects this takes a negligible amount of time (a few seconds or less); for large projects, it can take longer.

Most of our users do not mind this cost as the power and safety of type-aware static analysis rules is worth the tradeoff. Additionally, most users primarily consume lint errors via IDE plugins which, through caching, do not suffer the same penalties. This means that generally they usually only run a complete lint before a push, or via their CI, where the extra time often doesn't matter.

We strongly recommend you do use type-aware linting, but the above information is included so that you can make your own, informed decision.

Troubleshooting​

If you're having problems getting this working, please have a look at our Troubleshooting and FAQs page.