Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings
This repository was archived by the owner on Mar 7, 2025. It is now read-only.

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

U-4-E-A started this conversation inGeneral
Discussion options

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-checkconst { 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.

You must be logged in to vote

Replies: 1 comment 11 replies

Comment options

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?

You must be logged in to vote
11 replies
@U-4-E-A
Comment options

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

}    typescript.tsserver.experimental.enableProjectDiagnostics: true}

If that is set totrue, it breaksv2.0.0 of the package. If it is set tofalse, 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 theeslint-define-config package or do I have to change my settings?

@Shinigami92
Comment options

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

@U-4-E-A
Comment options

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

@Shinigami92
Comment options

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
Comment options

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 withv1.24.1, which seems to be doing everything I want for now.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Category
General
Labels
None yet
2 participants
@U-4-E-A@Shinigami92
[8]ページ先頭
©2009-2025 Movatter.jp