Bug: Props detection broken with jest since 2.4.2 (works in 2.4.1) about vue-jest HOT 7 OPEN

You are right of course :) I'll update the issue.

from vue-jest.

Hi @sawmurai

Thanks for the repro.
I think the regression occurred between v2.4.1 and v2.4.2 no? Because v2.4.2 was the release with vuejs/test-utils@1db42c8 which changed the props() type.

from vue-jest.

@johnsoncodehk would you mind taking a look at why vuejs/test-utils@1db42c8 introduced this regression? How should we type props() to avoid that?

cc @alecgibson as well, as the original author of this change

from vue-jest.

Weirdly if I download this repro and run locally in VS Code, it seems fine:

npm run build also works fine

from vue-jest.

It even correctly flags bad props:

and fails npm run build:

❯ npm run build

> [email protected] build
> vue-tsc && vite build

src/components/HelloWorld.spec.ts:14:26 - error TS2339: Property 'foo' does not exist on type '{ readonly msg: string; key?: string | number | symbol | undefined; ref?: VNodeRef | undefined; ref_for?: boolean | undefined; ref_key?: string | undefined; onVnodeBeforeMount?: VNodeMountHook | ... 1 more ... | undefined; ... 6 more ...; style?: unknown; } & Partial<...> & Omit<...>'.

14   expect(wrapper.props().foo).toBe('Hello world');
                            ~~~


Found 1 error in src/components/HelloWorld.spec.ts:14

from vue-jest.

Oh I see, npm run build passes, but running jest fails. This feels like a jest misconfiguration, or an issue with the @vue/vue3-jest transformer or its configuration

Edit: or the ts-jest transformer could also be the issue

from vue-jest.

Thanks for looking into it @alecgibson !
I'll transfer to the vue-jest repo then, as it does feel like a Jest specific issue 👍

from vue-jest.