From c900b069b0a9c88e2812435ecb5389dc0a61a250 Mon Sep 17 00:00:00 2001 From: cexbrayat Date: Mon, 30 Aug 2021 10:51:40 +0200 Subject: [PATCH] fix: remove hasOwnProperty workaround vue-test-utils-next now uses jest v27.1+, which includes a fix for hasOwnPropery (see https://github.com/facebook/jest/pull/11721). This allows to remove the dirty workaround we had in our codebase, but users will have to update to Jest v27.1+. --- src/mount.ts | 4 ---- 1 file changed, 4 deletions(-) diff --git a/src/mount.ts b/src/mount.ts index f3c383d961..74df2cfa00 100644 --- a/src/mount.ts +++ b/src/mount.ts @@ -464,10 +464,6 @@ export function mount( // if not, use the return value from app.mount. const appRef = vm.$refs[MOUNT_COMPONENT_REF] as ComponentPublicInstance const $vm = Reflect.ownKeys(appRef).length ? appRef : vm - // we add `hasOwnProperty` so jest can spy on the proxied vm without throwing - $vm.hasOwnProperty = (property) => { - return Reflect.has($vm, property) - } console.warn = warnSave return createWrapper(app, $vm, setProps) }