fix(types): Fix mount and shallowMount types

[pikax]

fix #251

This was caused because vue-class-component dependency was not made optional or as a dev, so the import VueContructor would always be any, making all the mount and shallowMount to be caught by that overload.

I've removed the dependency on VueContructor on the mount, made it a bit more generic, this might break if the types changes on the vue-class-component (which I think is unlikely)

@ktsn can you just validate if this overload is enough?

// Class component - no props
export function mount<V>(
  originalComponent: {
    new (...args: any[]): V
    registerHooks(keys: string[]): void
  },
  options?: MountingOptions<any>
): VueWrapper<ComponentPublicInstance<V>>

// Class component - props
export function mount<V, P>(
  originalComponent: {
    new (...args: any[]): V
    props(Props: P): any
    registerHooks(keys: string[]): void
  },
  options?: MountingOptions<P>
): VueWrapper<ComponentPublicInstance<V>>

[ktsn]

Suggested change

	export function mount<V, P>(
	originalComponent: {
	new (...args: any[]): V
	props(Props: P): any
	registerHooks(keys: string[]): void
	},
	options?: MountingOptions<P>
	): VueWrapper<ComponentPublicInstance<V>>
	export function mount<V extends ComponentPublicInstance<P>, P>(
	originalComponent: {
	new (...args: any[]): V
	},
	options?: MountingOptions<P>
	): VueWrapper<V>

As class component implements component public instance, just using the interface should be enough.

[pikax]

That's a bit too lenient, because the defineComponent will also return a valid component public instance to be used on JSX

[lmiller1990]

Yep, agree, having props intellisense is pretty cool. I don't think it's possible for data in class component though.

[lmiller1990]

@pikax is this good to go? Seems fine to me - are you still thinking about this typing or should we merge and release this?

[pikax]

@lmiller1990 I'm good with this typing