Getting typescript errors reported with js files

The readme says this works with both ts and js yet when I run npx eslint webpack.config.js I’m seeing lots of ts errors such as:

1:22  error    Require statement not part of import statement              @typescript-eslint/no-var-requires
   2:27  error    Require statement not part of import statement              @typescript-eslint/no-var-requires
   2:35  error    Unable to resolve path to module 'copy-webpack-plugin'      import/no-unresolved
   3:30  error    Require statement not part of import statement              @typescript-eslint/no-var-requires
   3:38  error    Unable to resolve path to module 'mini-css-extract-plugin'  import/no-unresolved
   4:14  error    Require statement not part of import statement              @typescript-eslint/no-var-requires
  30:24  warning  Missing return type on function                             @typescript-eslint/explicit-function-return-type

I’m using the base configuration.

.eslintrc:

{
  "root": true,
  "extends": [
    "airbnb-typescript/base",
    "plugin:@typescript-eslint/recommended",
    "plugin:prettier/recommended"
  ],
  "parser": "@typescript-eslint/parser",
  "plugins": ["@typescript-eslint"]
}

Using latest versions except eslint@6.8.0.

[nero120]

Fair enough. Yes the tsconfig.eslint.json solution does indeed sort it, many thanks for all of your help @iamturns!

[iamturns]

Yeah I agree, it is a bit annoying. This is how @typescript-eslint/parser behaves. I’m sure there’s a good reason, but I haven’t looked into it. The tsconfig.eslint.json solution is a slight annoyance, but does the job!