How to fix Type information for @typescript-eslint rule unavailable in TypeScript

What this error means

The "Type information for @typescript-eslint rule unavailable" error appears when you're using ESLint rules that require TypeScript's type checker (like @typescript-eslint/await-thenable, @typescript-eslint/no-floating-promises, or @typescript-eslint/strict-boolean-expressions), but your ESLint configuration hasn't been set up to provide parser services with type information. These type-aware rules need access to TypeScript's type system to analyze your code properly. Unlike syntax-based rules that only look at the code structure, type-aware rules need to understand what types your variables have, what functions return, and other semantic information that requires TypeScript compilation. The @typescript-eslint/parser needs to be configured with either parserOptions.projectService (recommended as of v8) or parserOptions.project to enable this functionality. Without this configuration, the parser cannot generate the type information that these advanced rules require.

Typical symptoms

• ESLint error message: 'Type information for rule X unavailable'
• Type-aware rules like no-floating-promises fail to lint
• Error appears when using @typescript-eslint rules requiring type checking
• IDE shows warnings that ESLint rules cannot access type information
• Linting works for syntax rules but fails for semantic/type-aware rules
• Error occurs after adding type-aware rules to ESLint configuration

Common causes

1. parserOptions.projectService or parserOptions.project not configured in .eslintrc
2. Using type-aware rules without enabling typed linting in ESLint config
3. Files being linted are not included in the tsconfig.json project
4. ESLint configuration is missing the @typescript-eslint/parser entirely
5. Multiple tsconfig.json files with incorrect project references
6. Using an outdated version of @typescript-eslint that doesn't support projectService
7. parserOptions configured incorrectly with wrong path to tsconfig.json

How to fix "Type information for @typescript-eslint rule unavailable"

// .eslintrc.js or .eslintrc.cjs
module.exports = {
  parser: '@typescript-eslint/parser',
  parserOptions: {
    projectService: true,
    tsconfigRootDir: __dirname,
  },
  plugins: ['@typescript-eslint'],
  extends: [
    'eslint:recommended',
    'plugin:@typescript-eslint/recommended',
    'plugin:@typescript-eslint/recommended-requiring-type-checking',
  ],
};

// eslint.config.js
import tseslint from '@typescript-eslint/eslint-plugin';
import parser from '@typescript-eslint/parser';

export default [
  {
    files: ['**/*.ts', '**/*.tsx'],
    languageOptions: {
      parser,
      parserOptions: {
        projectService: true,
        tsconfigRootDir: import.meta.dirname,
      },
    },
    plugins: {
      '@typescript-eslint': tseslint,
    },
    rules: tseslint.configs['recommended-type-checked'].rules,
  },
];

// .eslintrc.js
module.exports = {
  parser: '@typescript-eslint/parser',
  parserOptions: {
    project: './tsconfig.json',
    tsconfigRootDir: __dirname,
  },
  plugins: ['@typescript-eslint'],
  extends: [
    'plugin:@typescript-eslint/recommended-requiring-type-checking',
  ],
};

module.exports = {
  parser: '@typescript-eslint/parser',
  parserOptions: {
    project: [
      './tsconfig.json',
      './packages/*/tsconfig.json',
      './apps/*/tsconfig.json',
    ],
    tsconfigRootDir: __dirname,
  },
};

{
  "compilerOptions": {
    "strict": true,
    // ... other options
  },
  "include": [
    "src/**/*",
    "tests/**/*",
    "*.config.ts"
  ],
  "exclude": [
    "node_modules",
    "dist",
    "build"
  ]
}

{
  "extends": "./tsconfig.json",
  "include": [
    "src/**/*",
    "tests/**/*",
    "*.config.ts",
    ".eslintrc.ts"
  ]
}

parserOptions: {
  project: './tsconfig.eslint.json',
  tsconfigRootDir: __dirname,
}

# Install @typescript-eslint packages
npm install --save-dev @typescript-eslint/parser @typescript-eslint/eslint-plugin

# Or with yarn
yarn add -D @typescript-eslint/parser @typescript-eslint/eslint-plugin

# Or with pnpm
pnpm add -D @typescript-eslint/parser @typescript-eslint/eslint-plugin

npm install --save-dev @typescript-eslint/parser@latest @typescript-eslint/eslint-plugin@latest

npm list @typescript-eslint/parser @typescript-eslint/eslint-plugin

// .eslintrc.js
module.exports = {
  // ... main config with projectService
  overrides: [
    {
      // Disable type-aware linting for JavaScript files
      files: ['*.js'],
      extends: ['plugin:@typescript-eslint/disable-type-checked'],
    },
    {
      // Disable for config files not in tsconfig
      files: ['.*.js', '*.config.js'],
      parserOptions: {
        project: null,
      },
      rules: {
        '@typescript-eslint/await-thenable': 'off',
        '@typescript-eslint/no-floating-promises': 'off',
      },
    },
  ],
};

module.exports = {
  ignorePatterns: ['dist/', 'build/', 'coverage/', '*.config.js'],
  // ... rest of config
};

# Run ESLint manually to verify
npx eslint src/

# Or through npm scripts
npm run lint

# Remove cached ESLint results
rm -rf node_modules/.cache/eslint

# Or use ESLint's cache flag
npx eslint . --cache-strategy content

Advanced notes

// Old config (project)
parserOptions: {
  project: ['./tsconfig.json', './packages/*/tsconfig.json'],
  tsconfigRootDir: __dirname,
}

// New config (projectService)
parserOptions: {
  projectService: true,
  tsconfigRootDir: __dirname,
}

overrides: [
  {
    files: ['src/**/*.ts'],
    extends: ['plugin:@typescript-eslint/recommended-type-checked'],
  },
  {
    files: ['tests/**/*.ts'],
    // Only use syntax rules for tests
    extends: ['plugin:@typescript-eslint/recommended'],
  },
]

npx eslint . --cache --cache-location node_modules/.cache/eslint

# Run type checking separately
npm run type-check  # tsc --noEmit

# Run ESLint with only syntax rules
npm run lint:syntax

parserOptions: {
  projectService: {
    allowDefaultProject: ['*.js'],
    defaultProject: './tsconfig.json',
  },
  tsconfigRootDir: __dirname,
}

# If ESLint can't get types, verify TypeScript works
npx tsc --noEmit

# Trace module resolution
npx tsc --traceResolution | grep "yourfile.ts"

// debug-rule.js
module.exports = {
  rules: {
    'debug-parser': {
      create(context) {
        const services = context.parserServices;
        console.log('Has type checker:', !!services?.program);
        return {};
      },
    },
  },
};

// DON'T USE - deprecated and slow
parserOptions: {
  createDefaultProgram: true,
}

// tsconfig.json
{
  "references": [
    { "path": "./packages/core" },
    { "path": "./packages/utils" }
  ]
}

parserOptions: {
  project: './tsconfig.json',
  // This will follow references automatically
}

// ESM flat config
import { dirname } from 'path';
import { fileURLToPath } from 'url';

const __dirname = dirname(fileURLToPath(import.meta.url));

export default [
  {
    languageOptions: {
      parserOptions: {
        projectService: true,
        tsconfigRootDir: __dirname,
      },
    },
  },
];

Frequently asked questions

What does "Type information for @typescript-eslint rule unavailable" mean?

The "Type information for @typescript-eslint rule unavailable" error appears when you're using ESLint rules that require TypeScript's type checker (like @typescript-eslint/await-thenable, @typescript-eslint/no-floating-promises, or @typescript-eslint/strict-boolean-expressions), but your ESLint configuration hasn't been set up to provide parser services with type information. These type-aware rules need access to TypeScript's type system to analyze your code properly. Unlike syntax-based rules that only look at the code structure, type-aware rules need to understand what types your variables have, what functions return, and other semantic information that requires TypeScript compilation.

How do I fix "Type information for @typescript-eslint rule unavailable"?

This error occurs when you're using type-aware ESLint rules from @typescript-eslint but haven't configured the parser to provide type information. The fix involves configuring parserOptions with either projectService or project in your ESLint configuration file.

What causes "Type information for @typescript-eslint rule unavailable"?

parserOptions.projectService or parserOptions.project not configured in .eslintrc Using type-aware rules without enabling typed linting in ESLint config Files being linted are not included in the tsconfig.json project

Is the "Type information for @typescript-eslint rule unavailable" error serious?

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

Related errors

• 'esModuleInterop' and 'allowSyntheticDefaultImports' require module resolution

  'esModuleInterop' and 'allowSyntheticDefaultImports' require module resolution

  MEDIUM

• @typescript-eslint rule 'X' requires parser

  How to fix '@typescript-eslint rule requires parser' error

  MEDIUM

• 'exactOptionalPropertyTypes' requires strict mode

  How to fix 'exactOptionalPropertyTypes requires strict mode' in TypeScript

  MEDIUM

• Cannot resolve TypeScript service in @typescript-eslint

  How to fix 'Cannot resolve TypeScript service in @typescript-eslint' error

  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 - Linting with Type Information(Official Docs)
• 📖
  typescript-eslint - Parser Documentation(Official Docs)
• typescript-eslint - parserOptions.project = true
• 📖
  typescript-eslint - Typed Linting Troubleshooting(Official Docs)
• Jacob Paris - Solve parserOptions.project bug
• 🐙
  typescript-eslint GitHub - parserOptions.project Issues(GitHub)
• BobbyHadz - parserOptions.project Configuration
• 📖
  typescript-eslint - General FAQs(Official Docs)