Expected Behavior Creating new ESLintPlu

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Remove defaults for extensions about eslint-webpack-plugin HOT 2 CLOSED

webpack-contrib commented on August 31, 2024 3

Remove defaults for extensions

from eslint-webpack-plugin.

Comments (2)

waldronmatt commented on August 31, 2024

I spent a few hours trying to figure out a workaround to this.

For anyone looking to have this plugin work with a mixed project (.ts and .js), what worked for me was specifying both 'js' and 'ts' extensions in the plugin:

webpack-dev-config:

    new ESLintPlugin({
      extensions: ['js', 'ts'],
    }),

and in my .eslintrc.js file:

setting up babel-eslint as normal for my .js files
setting up @typescript-eslint/parser for .ts files via overrides:

module.exports = {
  parser: "babel-eslint",
  plugins: ["prettier"],
  extends: ["airbnb-base", "prettier"],
  env: {
    node: true,
    browser: true,
  },
  rules: {
    "prettier/prettier": ["error"],
  },
  overrides: [
    {
      files: ["**/*.ts"],
      parser: "@typescript-eslint/parser",
      plugins: ["@typescript-eslint", "prettier"],
      parserOptions: {
        project: "./tsconfig.eslint.json",
      },
      extends: [
        "airbnb-typescript/base",
        "plugin:@typescript-eslint/recommended",
        "prettier",
        "prettier/@typescript-eslint",
      ],
      env: {
        node: true,
        browser: true,
      },
      rules: {
        "prettier/prettier": ["error"],
      },
    },
  ],
};

Now when I run webpack, I'm getting the expected ts-specific typing errors for my .ts files, and typical errors for my .js files: