Typescript style-only imports are not resolving correctly

[mjbvz]

From @ksnyde on July 1, 2018 17:43

• VSCode Version: Version 1.24.1 (1.24.1)
• OS Version: macOS 10.13.5

Steps to Reproduce:

1. use tsc to transpile (using TS 3.0.0-dev.20180603) project with dynamic import like:

   private static _defaultDb: import("abstracted-firebase").RealTimeDB;

2. run tsc with the following tsconfig.json:

   {
     "compilerOptions": {
       "declaration": true,
       "module": "esnext",
       "target": "es2017",
       "lib": ["es2017", "esnext.asynciterable", "es2015.reflect"],
       "moduleResolution": "node",
       "sourceMap": true,
       "noImplicitAny": true,
       "experimentalDecorators": true,
       "emitDecoratorMetadata": true,
       "outDir": "./dist/esnext",
       "removeComments": false,
       "typeRoots": ["./node_modules/@types"]
     },
     "include": ["src/**/*"],
     "exclude": ["node_modules/**/*", "node_modules/@firebase/**/*.d.ts"]
   }

No errors are reported but if you go into the .d.ts file where the import existed you'll find a transpilation similar to:

    protected _db: import("../../../../../../Users/ken/mine/forest-fire/firemodel/src/decorators/schema").RealTimeDB;

Does this issue occur when all extensions are disabled?: Yes

Copied from original issue: microsoft/vscode#53400

[DanielRosenwasser]

Looks like one of

• Import types in d.ts files contain relative paths to node_modules #24599
• typescript@next (and 2.9.x) outputs node_modules relative path to imports #25345
• auto import broken that import as a relative path #25186

Can you try out our nightly (npm install -g typescript@next) and see if you're able to reproduce the issue?

[ghost]

Fix should just have been merged with #25364, please try with typescript@next.