title: eslint complains about typescript's path aliasing
body: <p>I've set up path aliasing in typescript's <code>.tsconfig</code> so my imports look cleaner.</p>
  
  <p>In my code when I try and import my interface like this</p>
  
  <pre><code>import { ApiResponse } from '@api';
  </code></pre>
  
  <p>eslint complains: <code>Unable to resolve path to module '@api'</code>
  However, intelisense in vscode seems fine. Its able to give code prediction and "Jump to declaration" which is a clue that my <code>.tsconfig</code> is set up correctly but eslint is somehow misconfigured. </p>
  
  <hr>
  
  <h2>Relevant files</h2>
  
  <p>In my <strong>tsconfig.json</strong>, I've set up path aliasing like so:</p>
  
  <pre><code>{
    "compilerOptions": {
      "moduleResolution": "node",               
      "baseUrl": "./src",                     
      "paths": {                              
        "@api": ["./types/api"]
      },
    }
  }
  </code></pre>
  
  <p>My <strong>./src/types/api.ts</strong> looks like this:</p>
  
  <pre><code>// 3rd party API response object
  export interface ApiResponse {
    ....
  }
  </code></pre>
  
  <p>Finally, my <strong>.eslintrc.json</strong> looks like this:</p>
  
  <pre><code>{
    "env": {
      "node": true
    },
    "globals": {
      "console": true
    },
    "plugins": ["@typescript-eslint", "prettier"],
    "parser": "@typescript-eslint/parser",
    "settings": {
      "import/extensions": [".js", ".ts"],
      "import/parsers": {
        "@typescript-eslint/parser": [".ts"]
      },
      "import/resolver": {
        "node": {
          "extensions": [".js", ".ts"]
        }
      }
    }
  }
  
  
  </code></pre>
  
  <p>Any idea what I may be doing wrong?</p>