acceptHMRUpdate type error when switching to TS 5.0

[josh-hemphill]

Reproduction

https://github.com/josh-hemphill/pinia_bug-report

Steps to reproduce the bug

1. Use Typescript >5.0
2. Use Setup-style to create a store
3. Use Hot module reload snippet if not present (acceptHMRUpdate function)
4. Set VSCode to use workspace tsc or run tsc --noEmit
5. Observe the error

Expected behavior

For there not to be a type error

Actual behavior

Type error is thrown:

Argument of type 'StoreDefinition<"counter", _UnwrapAll<Pick<{ n: Ref<number>; getN: () => Ref<number>; }, "n">>, Pick<{ n: Ref<number>; getN: () => Ref<number>; }, never>, Pick<...>>' is not assignable to parameter of type 'StoreDefinition<string, StateTree, _GettersTree<StateTree>, _ActionsTree>'.
  Property 'getN' is missing in type '_ActionsTree' but required in type 'Pick<{ n: Ref<number>; getN: () => Ref<number>; }, "getN">'.ts(2345)

Additional information

No response

[samydoesit]

Not great, but adding as any to the first parameter of acceptHMRUpdate works around it on my end.

if (import.meta.hot) {
  import.meta.hot.accept(acceptHMRUpdate(useUserStore as any, import.meta.hot));
}

or add a shim

# shim-pinia.d.ts

// TODO: https://github.com/vuejs/pinia/issues/2098
declare module 'pinia' {
  // eslint-disable-next-line @typescript-eslint/no-explicit-any, @typescript-eslint/ban-types
  export function acceptHMRUpdate(initialUseStore: StoreDefinition | any, hot: any): (newModule: any) => any;
}

export {}

[posva]

Using as any for this particular case is fine. I will take a look in the future (I will remove the contribution welcome tag if I do) but feel free to take this if you want.