Have you ever configured a linter considering TypeScript typing?

Yes, configuring a linter with TypeScript typing considerations is a common practice to improve code quality.

Main points:

• ESLint is used with the @typescript-eslint plugin, which understands TypeScript syntax and types.
• The linter configuration includes the parser @typescript-eslint/parser, which analyzes code with TypeScript in mind.
• Rules can be configured to consider types, such as warning about unused variables considering their types or incorrect type usage.
• Rules that require explicit type annotations or prohibit the use of any can be enabled.

Example of a basic .eslintrc.json configuration:

{
  "parser": "@typescript-eslint/parser",
  "plugins": ["@typescript-eslint"],
  "extends": [
    "eslint:recommended",
    "plugin:@typescript-eslint/recommended"
  ],
  "rules": {
    "@typescript-eslint/no-unused-vars": ["error"],
    "@typescript-eslint/explicit-function-return-type": "warn"
  }
}

Thus, the linter helps not only with syntax but also with type safety, which is especially important in large TypeScript projects.