[ValentinYoushkevich]

Since #2946, a Teleport stubbed with a component (TeleportStub, or e.g. { template: '<div><slot /></div>' }) keeps the same stub type across renders, so its content is no longer remounted, but it is no longer updated either:

const Comp = { props: ['count'], template: '<div><Teleport to="body">{{ count }}</Teleport></div>' }
const wrapper = mount(Comp, { props: { count: 1 }, global: { stubs: { Teleport: TeleportStub } } })
await wrapper.setProps({ count: 2 })
wrapper.text() // '1'

The stub vnode keeps the patch flag compiled for the Teleport (0 with a static to), so in an optimized re-render of the parent Vue sees "no dynamic props, no dynamic slots" and skips the stub. The transformer now gives the stub vnode the BAIL patch flag, so its slot and props are always diffed (DYNAMIC_SLOTS alone is not enough: with a render function it makes Vue skip the props update, see the second test). #2958 uses the same flag, but also for non-stubbed Teleport/KeepAlive; here it is only set on the stub vnode.

Not released yet: 2.5.1 updated the content by remounting it. Real case: faveo's global Teleport: { template: '<div><slot /></div>' } stub (jest.setup.js) — the dropdown inside the Teleport of DatatableActions.vue never appears on main after clicking the toggle.

Playground (main e22514a vs 2.5.1)

[netlify]

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

Name	Link
🔨 Latest commit	f530dfc
🔍 Latest deploy log	https://app.netlify.com/projects/vue-test-utils-docs/deploys/6ae232b36d85eb412f3718bf
😎 Deploy Preview	https://deploy-preview-2993--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 project configuration.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@vue/test-utils@2993

commit: f530dfc

[cexbrayat]

Thanks 👍