tsconfig.json path aliases are not included in auto import paths

[mjbvz]

From @eodrap on July 21, 2018 16:0

VS Code version: Code 1.25.1 (1dfc5e557209371715f655691b1235b6b26a06be, 2018-07-11T15:33:29.235Z)
OS version: Darwin x64 17.6.0
TypeScript version: 2.9.2
Does this issue occur when all extensions are disabled?: Yes

Steps to reproduce -

1. Define path alias in tsconfig.json -

    "baseUrl": "./",
    "paths": {
      "@root/*": ["*"]
    },

2. Restart VS Code
3. Trigger auto import by typing a module name and selecting the, 'Auto import from ...' menu entry
4. The auto import path offered does not include the alias, a relative path is inserted -
   Module path x/y/z/module.ts
   Expected path @root/x/y/z/module.ts
   Inserted path x/y/z/module.ts

Omitting the alias is causing module not found errors.

#39459 suggests this has been resolved but I cannot find a way to include the alias path prefix in auto import suggestions. I've tried setting typescript.preferences.importModuleSpecifier = 'non-relative'. Apologies if I'm missing a required preference or doing something silly.

Copied from original issue: microsoft/vscode#54798

[mjbvz]

From @vscodebot[bot] on July 21, 2018 16:0

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• TypeScript Auto Import only uses relative paths (#54513)

[mjbvz]

From @eodrap on July 23, 2018 9:33

Thanks for replying, yes it does. Clean installation & profile of VS Code Insiders, no installed extensions, and auto import paths do not include the configured alias. The alias is understood if added manually to import paths.

VS Code version: Code - Insiders 1.26.0-insider (26e5a55, 2018-07-20T05:11:33.977Z)
OS version: Darwin x64 17.6.0

[mjbvz]

Confirmed this on typescript@3.1.0-dev.20180721

We always seem to use use the shorter path relative to baseUrl instead of the one configured in paths