Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Findings not visible in editor. #1852

Closed
fudom opened this issue Jun 3, 2024 · 1 comment
Closed

Findings not visible in editor. #1852

fudom opened this issue Jun 3, 2024 · 1 comment

Comments

@fudom
Copy link

fudom commented Jun 3, 2024

Just updated from eslint 8 to 9. It seems that this extension (v2.4.4) does not show the findings in editor anymore. I see no erros on eslint output panel.

eslint.config.mjs

import pluginJs from '@eslint/js';
import globals from 'globals';
import tseslint from 'typescript-eslint';

export default [
  {
    languageOptions: { globals: globals.browser },
  },
  {
    ignores: ['/*', '!/src', '**/*.spec.ts', 'src/assets/*'],
  },
  pluginJs.configs.recommended,
  ...tseslint.configs.recommended,
  {
    files: ['**/*.ts'],
    rules: {
      '@typescript-eslint/no-empty-function': 'warn',
    },
  },
];

CLI shows warnings/erros. But I see nothing in VSCode anymore. Is this a known issue?

@fudom
Copy link
Author

fudom commented Jun 4, 2024

It seems that this is an experimental feature that needs to be enabled. Flat config is the new default of ESLint. A breaking change indeed. Is a version with official support planned (leaving experimental)?

settings.json

"eslint.experimental.useFlatConfig": true

Update: #1644

@fudom fudom closed this as completed Jun 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant