Thanks :)

Will need to find some time to test this and possibly try and add actual types for the ``Portalcomponent instead ofany`, but this is immensly helpful :)

Yeah, SFC's are shimmed as any in the Vue CLI, and I think it tends to avoid more problems than it would solve by being typed as a proper component, but I would love to know if there's a better way.

Here's one possible way to type the component, but it has the drawback of advertising internal methods:

import Vue, { Component, PluginFunction } from 'vue'

export interface SimplePortalOptions {
  name?: string
}

export interface SimplePortalConfig {
  selector: string
}

export var config: Readonly<SimplePortalConfig>
export var setSelector: <T extends string>(selector: T) => T

interface PortalMethods {
  getTargetEl(): void | HTMLElement | null
  insertTargetEl(): void
  mount(): void
  unmount(): void
}

export interface PortalProps {
  disabled?: boolean
  prepend?: boolean
  selector?: string
  tag?: string
}

export var Portal: Component<void, PortalMethods, void, PortalProps>

var install: PluginFunction<SimplePortalOptions>
export default install

Any chance of this getting merged and pushed as a package update? Typescript support would be useful.

Hello guys,
any chance that this is going to be merged?

For those who need TS definition, you can create a .d.ts file in your src folder with that definition, it should work:

declare module '@linusborg/vue-simple-portal' {
  import { PluginFunction } from 'vue'

  export interface SimplePortalOptions {
    name?: string
  }

  export interface SimplePortalConfig {
    selector: string
  }

  export const config: Readonly<SimplePortalConfig>
  export const setSelector: <T extends string>(selector: T) => T
  export const Portal: any

  const install: PluginFunction<SimplePortalOptions>
  export default install
}