Bring Your Own Parser

This package intentionally does not ship:

• languageOptions.parser
• plugins
• files globs

Because projects differ (monorepos, project references, TS config paths, parserOptions).

Why?

This design choice is core to our philosophy of composable, conflict-free tooling. Read more about the Bring Your Own Parser principle in our Philosophy page.

Typical wiring

Using the typescript-eslint meta-package:

import tseslint from 'typescript-eslint';
import namingConfig from 'eslint-config-naming';

export default [
  {
    files: ['**/*.ts', '**/*.tsx'],
    languageOptions: {
      parser: tseslint.parser,
      parserOptions: {
        project: ['./tsconfig.json'],
        tsconfigRootDir: import.meta.dirname,
      },
    },
    plugins: { '@typescript-eslint': tseslint.plugin },
  },
  ...namingConfig,
];

Using explicit packages (@typescript-eslint/parser and @typescript-eslint/eslint-plugin):

import tsParser from '@typescript-eslint/parser';
import tsPlugin from '@typescript-eslint/eslint-plugin';
import namingConfig from 'eslint-config-naming';

export default [
  {
    files: ['**/*.ts', '**/*.tsx'],
    languageOptions: {
      parser: tsParser,
      parserOptions: {
        project: ['./tsconfig.json'],
        tsconfigRootDir: import.meta.dirname,
      },
    },
    plugins: { '@typescript-eslint': tsPlugin },
  },
  ...namingConfig,
];

Both approaches work identically — typescript-eslint simply re-exports the parser and plugin.

Common parserOptions

• project: enable type-aware rules (recommended)
• tsconfigRootDir: monorepos / custom locations
• sourceType: usually module