ESLint complains about unused variable when variable of it is used to define Typescript parameter type

[justin13888]

Tell us about your environment

• ESLint Version: 6.8.0
• Node Version: 12.16.3
• npm Version: 6.14.5

What parser (default, Babel-ESLint, etc.) are you using?
@typescript-eslint/parser
Please show your full configuration:

Configuration

{
    "env": {
        "es6": true,
        "node": true
    },
    "extends": [
        "google"
    ],
    "globals": {
        "Atomics": "readonly",
        "SharedArrayBuffer": "readonly"
    },
    "parser": "@typescript-eslint/parser",
    "parserOptions": {
        "ecmaVersion": 2018,
        "sourceType": "module"
    },
    "plugins": [
        "@typescript-eslint"
    ],
    "rules": {
        "indent": [
            "error",
            4
        ],
        "require-jsdoc": 0
    }
}

What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.

import * as Discord from 'discord.js';
export class CommandService {
    parseCommand(msg: Discord.Message) {
        // if (msg instanceof Discord.Message) console.log('');
    }
}

eslint "**/*.ts"

What did you expect to happen?
Should have no error.

What actually happened? Please include the actual, raw output from ESLint.
services/command.service.ts
1:13 error 'Discord' is defined but never used no-unused-vars

✖ 1 problem (1 error, 0 warnings)

Are you willing to submit a pull request to fix this bug?
Don't know how.

[anikethsaha]

You need to extend typescript-eslint rules if you are using it for typescript.
for no-unused-vars, use this rule and no-unused-vars-experimental.

[justin13888]

Thanks. Really hope they implement the work around soon.

[anikethsaha]

Really hope they implement the work around soon.

eslint supports typescript through typescript-eslint project. So I guess it is expected behavior.

[justin13888]

The code you mentioned isn't automatically generated when using eslint --init. So others may easily face this issue as well in the future.

[mdjermanovic]

The code you mentioned isn't automatically generated when using eslint --init. So others may easily face this issue as well in the future.

This should be fixed with #13235