RFC: Auto register for types

Context:

• https://github.com/antfu/unplugin-auto-import/pull/60#issuecomment-939341877
• https://github.com/antfu/vue-global-api/issues/10

For example, it would be great to have common types like Ref, ComputedRef globally available when using the Vue preset. I would expect the API to be like

{
  // auto importing for import
  imports: [
    'vue'
  ],
  // auto importing for types
  types: [
    'vue', // again, we could have presets for it.
    {
      vue: ['Ref', 'ComputedRef']
    }
  ]
}

[terran42]

@antfu Maybe I misunderstood, but is this not what you want?

• https://stackblitz.com/edit/node-v1ncfz?file=imports.d.ts%3AL11
• https://stackblitz.com/edit/node-v1ncfz?file=global.d.ts%3AL2-L2 (commented out, but works too when L11 in imports.d.ts is commented out)

Both seems to work, at least to my needs:

• Ref<number> in index.ts has hint type Ref<T> = Ref<any>
• Cmd+Click directs me to the right place in imports.d.ts or global.d.ts
• Cmd+Click in imports.d.ts or global.d.ts on V.Ref or import('vue').Ref leads to definitions in Vue.

I’m happy with that.

[userquin]

Right now I include global types on d.ts file using:

// Generated by 'unplugin-auto-import'
// We suggest you to commit this file into source control
import type {
  ComputedRef as __ComputedRef,
  Ref as __Ref  
} from 'vue'

declare global {
  type ComputedRef<T> = __ComputedRef<T>
  type Ref<T> = __Ref<T>
  const computed: typeof import('vue')['computed']
  ...
}
export{}

maybe we can use this another approach as suggested on issue on vue-global-api repo (both approaches work in IntelliJ, this latter would simplify the logic to generate the d.ts file and avoid adding redundant imports):

// Generated by 'unplugin-auto-import'
// We suggest you to commit this file into source control
declare global {
  type ComputedRef<T> = import('vue').ComputedRef<T>
  type Ref<T> = import('vue').Ref<T>
  const computed: typeof import('vue')['computed']
  ...
}
export {}