fix: update default vue 3 typescript shim

[jeneser]

#6021 eslint warns about "unsafe any" in default shim when formatting.

What kind of change does this PR introduce? (check at least one)

• Bugfix
• Feature
• Code style update
• Refactor
• Docs
• Underlying tools
• Other, please describe:

Does this PR introduce a breaking change? (check one)

• Yes
• No

Other information:

using unknown / never is good enough, or using any with a disable comment explaining why it's safe is a much better alternative. typescript-eslint/typescript-eslint#1071 (comment)

[haoqunjiang]

@cexbrayat @pikax I'm no expert in TypeScript so I'm not sure which is the better way to shim .vue type, using unknown or any with an eslint-disable-line comment. Do you have any opinion on this?

From what I understand, unknown is not assignable to any other type, so seems using the unknown type may break some real-world use cases? I haven't encountered any but I'm concerned about that.

[cexbrayat]

I think unknown is going to be painful, as wrapper.vm.something will be typed as never in unit tests, forcing developers to cast vm themselves every time. I do agree that any is not ideal, but it allows to write unit tests without too much trouble. I sadly don't think we can do better right now.

2 possible ways to deal with the issue with eslint:

• add a simple eslint-disable-next-line no-any in the shim
• or exclude d.ts files from eslint (my favorite, as it makes no real sense for eslint to analyze the shim)

[bodograumann]

The rule could also be @typescript-eslint/no-explicit-any.

[ziazon]

consider changing the shim to:

declare module '*.vue' {
  import type { DefineComponent } from 'vue';
  const component: DefineComponent<
    Record<string, unknown>,
    Record<string, unknown>,
    unknown
  >;
  export default component;
}