Why is eslint-define-config not picking up @eslint-types/typescript-eslint errors?

[U-4-E-A]

Firstly, I have @eslint-types/typescript-eslint installed.

I have it set up exactly as per the example here: -

https://www.npmjs.com/package/eslint-define-config#usage

// @ts-check
const { defineConfig } = require('eslint-define-config')

/// <reference types="@eslint-types/typescript-eslint" />

module.exports = defineConfig({
  parserOptions: {
    project: './tsconfig.json'
  },
  parser: '@typescript-eslint/parser',
  plugins: ['@typescript-eslint'],
  rules: {
    '@typescript-eslint/adjacent-overload-signatures': ['error']
  }
})

However, if I put a deliberate error (typo) in the rule name ("@typescript-eslint/adjacent-1234567890") I do not get an error. The error does however work for the standard eslint types - it is specifically the @eslint-types/typescript-eslint errors that are not showing.

What am I doing wrong? Thanks.

[Shinigami92]

with the context you given, everything should work fine, assuming you also installed everything needed
would you like to setup a minimal reproducible repo/stackblitz, so I could investigate what's missing?

[U-4-E-A]

OK, through trial and error, I have found the culprit in my vcode settings: -

}
    typescript.tsserver.experimental.enableProjectDiagnostics: true
}

If that is set to true, it breaks v2.0.0 of the package. If it is set to false, it works just fine.

A bit more about this setting can be found here: -

https://stackoverflow.com/questions/55201424/how-to-get-vscode-to-show-typescript-errors-for-files-not-open-in-the-editor

Is this considered a bug in the eslint-define-config package or do I have to change my settings?

[Shinigami92]

I would say, because it works without that specific setting just fine, it's not a bug with eslint-define-config
especially when it is an "experimental" setting

[U-4-E-A]

Do you have any idea exactly why it is happening? Presumably there was a change between v1.24.1 and v2.0.0 that caused that issue to show up?

[Shinigami92]

Absolutely no
Maybe ask a question in VSCode repo or TypeScript repo, as you identified an issue with that experimental setting

[U-4-E-A]

I'll do that and get back to you if I get something concrete as to why it is happening.

For now - for convenience sake - I am sticking with v1.24.1, which seems to be doing everything I want for now.