`paths` not used for auto import

From https://github.com/Microsoft/vscode/issues/72931

TypeScript Version: 3.5.0-dev.20190430

Search Terms:

• paths
• auto import

Repo

1. clone https://github.com/ac566/typescript-auto-import-issue and open in vscode
2. In VS Code, set "typescript.preferences.importModuleSpecifier": "non-relative"
3. Open src/app/app1/test.ts
4. Delete the import for TestType
5. Try using a quick fix or auto import to add the impact back

Expected behavior: The import is added as import { TestType } from "@myLib/example_2";

The is expected since the tsconfig configures paths and the import of @myLib/example_2 was previously working properly:

{
    "compilerOptions": {
        "target": "es5",
        "module": "es2015",
        "moduleResolution": "node",
        "baseUrl": ".",
        "paths": {
            "@myLib/*": [
                "./src/lib/src/*/_index.ts"
            ]
        }
    }
}

Actual behavior: The import is added as import { TestType } from "@myLib/example_2/_index";

[nautilor]

In my case just by using in my settings

"typescript.preferences.importModuleSpecifier": "non-relative",

and then setting in my tsconfig compilerOptions.paths my root as the last options I was able to import files using path correctly

{
  "compilerOptions": {
    "baseUrl": "./",
    "paths": {
      "@model/*": ["src/model/*"],
      "@route/*": ["src/route/*"],
      "@constant/*": ["src/constant/*"],
      "@/*": ["src/*"]
    }
  },
}

This creates

import { JWT_CONFIG } from "@constant/jwt";

instead of

import { JWT_CONFIG } from "./constant/jwt";

or

import { JWT_CONFIG } from "@/constant/jwt";

which is what i was looking for.

[WanderWang]

I got a same issue