Auto import suggests from umd instead of module in ionic 3

[mjbvz]

From @surajrao on June 25, 2018 9:19

• VSCode Version: 1.24.1
• OS Version:Mac OS High Sierra (10.13.5)

Steps to Reproduce:

1. Start a new ionic project.

ionic start myApp tabs

2. Try to import a component from ionic-angular.

The auto import seems to import from ionic-angular/umd which has ionic-angular/umd/index.d.ts
instead of ionic-angular which also includes ionic-angular/index.d.ts.

This results in the below error on running.

    Uncaught Error: Cannot find module "."
        at webpackMissingModule (index.js:3)
        at e.code (index.js:3)
        at Object.<anonymous> (index.js:9)
        at __webpack_require__ (bootstrap 62d6a5897825ac327001:54)
        at Object.690 (slide.transition.ts:67)
        at __webpack_require__ (bootstrap 62d6a5897825ac327001:54)
        at Object.495 (main.js:1885)
        at __webpack_require__ (bootstrap 62d6a5897825ac327001:54)
        at Object.487 (notification-api.ts:6)
        at __webpack_require__ (bootstrap 62d6a5897825ac327001:54)

Related StackOverflow post: ionic-uncaught-error-cannot-find-module
Does this issue occur when all extensions are disabled?: Yes

Is this because of the ionic project structure or an issue with vscode import?

"ionic-angular": "3.9.2"
typescript version in workspace - 2.9.1

Copied from original issue: microsoft/vscode#52786

[mjbvz]

Using 3.0.0-dev-20180623, we get these suggestions:

With TS 2.6.x, we get the proper suggestion

[aparkertg]

Same issue here with IonicModule.

Auto import recommends "import { IonicModule } from 'ionic-angular/umd';" which generated the same exact errors.

I resolved it by manually adjusting to "import { IonicModule } from 'ionic-angular';"

In main.ts, I'm not getting any suggestions from ../../../node_modules in typescript@next:

There's an option to import from the original declaration, which is in node_modules/ionic-angular/umd/toast/toast.d.ts, but it's the second suggestion, and doesn't affect completions, so that seems to be working as intended.

@aparkertg What file are you in when you try the import? Also, what operating system are you on?

May be a duplicate of #25279. Could you test again with tomorrow's typescript@next release.
I've never been able to reproduce the original issue with /umd appearing at the end of recommended imports.