chore: bump to vue v3.2.34

[cexbrayat]

This is a repro to showcase the regressions we have with vue v3.2.34 (currently beta.1)

As you can see in the build, we are running into some TS issues:

FAIL  tests/features/compat.spec.ts
  ● Test suite failed to run

    tests/features/compat.spec.ts:176:23 - error TS2339: Property 'foo' does not exist on type 'ComponentPublicInstance<unknown, {}, {}, {}, {}, {}, unknown, {}, false, ComponentOptionsBase<any, any, any, any, any, any, any, any, any, {}, ComponentProvideOptions>>'.

    176     expect(wrapper.vm.foo).toBe('bar')
                              ~~~

 FAIL  tests/mountingOptions/mocks.spec.ts
  ● Test suite failed to run

    tests/mountingOptions/mocks.spec.ts:50:44 - error TS2339: Property 'id' does not exist on type 'CreateComponentPublicInstance<{ [x: string & `on${string}`]: ((...args: never) => any) | undefined; } | { [x: string & `on${string}`]: ((...args: any[]) => any) | undefined; }, {}, {}, {}, {}, ComponentOptionsMixin, ... 12 more ..., ComponentProvideOptions>'.
      Property 'id' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: { [x: string & `on${string}`]: ((...args: never) => any) | undefined; } | { [x: string & `on${string}`]: ((...args: any[]) => any) | undefined; }; ... 10 more ...; $watch(source: string | Function, cb: Function, options?: WatchOptions<...> | undefined): WatchStopHan...'.

    50           this.$router.push(`/posts/${this.id}`)

The PR also showcases why we need vuejs/core#5947
and a weird TS inference problem

[netlify]

✅ Deploy Preview for vue-test-utils-docs ready!

Name	Link
🔨 Latest commit	cc35833
🔍 Latest deploy log	https://app.netlify.com/sites/vue-test-utils-docs/deploys/6285eeff8b53ff00081cb0ee
😎 Deploy Preview	https://deploy-preview-1510--vue-test-utils-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[cexbrayat]

@pikax With your fix and mine, I was able to remove the workarounds to update to 3.2.34
But we still have the type-checking errors in tests. Any ideas?

 FAIL  tests/features/compat.spec.ts
  ● Test suite failed to run

    tests/features/compat.spec.ts:176:23 - error TS2339: Property 'foo' does not exist on type 'ComponentPublicInstance<unknown, {}, {}, {}, {}, {}, unknown, {}, false, ComponentOptionsBase<any, any, any, any, any, any, any, any, any, {}, ComponentProvideOptions>>'.

    176     expect(wrapper.vm.foo).toBe('bar')
                              ~~~

 FAIL  tests/mountingOptions/mocks.spec.ts
  ● Test suite failed to run

    tests/mountingOptions/mocks.spec.ts:50:44 - error TS2339: Property 'id' does not exist on type 'CreateComponentPublicInstance<{ [x: string & `on${string}`]: ((...args: never) => any) | undefined; } | { [x: string & `on${string}`]: ((...args: any[]) => any) | undefined; }, {}, {}, {}, {}, ComponentOptionsMixin, ... 12 more ..., ComponentProvideOptions>'.
      Property 'id' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: { [x: string & `on${string}`]: ((...args: never) => any) | undefined; } | { [x: string & `on${string}`]: ((...args: any[]) => any) | undefined; }; ... 10 more ...; $watch(source: string | Function, cb: Fun
chore: bump to vue v3.2.34
ction, options?: WatchOptions<...> | undefined): WatchStopHan...'.

    50           this.$router.push(`/posts/${this.id}`)

[pikax]

This is a more generic way to catch components, I've removed the other findComponent overloads and the tests still passed, still not sure if removing the other overloads would cause an issue

[cexbrayat]

Shouldn't these methods return a VueWrapper<T>?

[pikax]

Yes 🤦

[pikax]

Concerned about this change, not 100% sure what's happening here

[lmiller1990]

route.params[key] is typed like this

What is your concern?

[cexbrayat]

The concern is that we shouldn't have to explicitly specify the type: the inference is somehow broken with V3.2.34

[pikax]

Having to annotate the return type is something is there since V2, but this is not an issue with Vue test utils, is more a concern with Vue 3.2.34 release, all good on test utils IMO