VSCode "auto import" of ESM module broken in 2.6.11 with umd namespace

Version

2.6.11

Reproduction link

https://imgur.com/a/RxJz6fT

Steps to reproduce

Since the 2.6.11 my IDE (VSCode) now suggest me import Vue from the ‘vue/types/umd’ namespace instead of the ESModule ‘vue’

I’m using Vue 2.6.11 Vue-CLI 4.1.0 VScode 1.41.1 Typescript 3.7.4

What is expected?

Prior 2.6.11, VScode was suggesting to import Vue from 'vue'

What is actually happening?

VSCode is suggesting me to import Vue from 'vue/types/umd' see screenshot

---

maybe it’s releated to https://github.com/vuejs/vue/pull/9912 ?

[chuckmah]

@octref from you example if you add Typescript you will have the auto-import suggesting by clicking on the 💡 from VSCode.

here’s how i reproduced it using minimal deps (not the vue-cli)

mkdir foo
cd foo
yarn add typescript vue vue-property-decorator
npx tsc --init --module "ES6" --lib "ES6" --target "ES6" --types "vue" --moduleResolution "Node"
touch TestVue.ts
code .

inside TestVue.ts

const component:Component = Vue.extend({});

The named import work i still get the suggestion to import from ‘vue’

But the default import do not appear

If i revert back to 2.6.10 i get the correct suggestion from the ‘vue’

Maybe it’s a TSServer issue 😕 … but because some of my dev on my team just use the suggested import regardless, i had to revert back to 2.6.10

[posva]

You should import it from vue-property-decorator like import { Component, Vue } from 'vue-property-decorator'

It looks like Vue is automatically imported within VSCode as creating an empty vue file already allows you to use Vue with correct typings, so I imagine it would make sense for the IDE to not be able to import automatically. I don’t know if this is something we can improve. @octref do you know if this is possible to change here or somewhere else?