chore: update npm/vue to use latest test utils

[lmiller1990]

• Closes In Cypress component testing, exposed values in a script setup component are not accessible on the component instance (AKA wrapper.vm) #26575

Additional details

Just updated the underlying vue/test-utils dependency to get some of the latest features, specifically, access variables declared and exposed via defineExpose.

I also fixed a bug where some of the Vue core code was incorrect bundled in the cypress/vue bundle. I fixed this by updating the external key in the rollup config. If you do cd npm/vue && yarn build && wc -l dist/cypress-vue.esm-bundler.js before and after, you'll see around 5k lines difference.

Steps to test

You can run the new test if you want, but as long as CI is passing, everything is 💯 . This is just a dependency update.

How has the user experience changed?

PR Tasks

• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

[cypress]

4 flaky tests on run #45951 ↗︎

0

5193

77

0

4

Details:

improve changelog and test
Project: cypress	Commit: 543437d762
Status: Passed	Duration: 14:30 💡
Started: May 2, 2023 1:54 AM	Ended: May 2, 2023 2:08 AM

  commands/net_stubbing.cy.ts • 1 flaky test • 5x-driver-electron

View Output Video

Test		Artifacts
network stubbing > intercepting request > can delay and throttle a StaticResponse		Output Video

  cypress/cypress.cy.js • 3 flaky tests • 5x-driver-electron

View Output Video

Test		Artifacts
... > correctly returns currentRetry		Output Video
... > correctly returns currentRetry		Output Video
... > correctly returns currentRetry		Output Video

_{This comment has been generated by cypress-bot as a result of this project's GitHub integration settings.}

[mike-plummer]

LGTM on the code side, just a couple minor tweaks needed

[cypress-bot]

Released in 12.12.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v12.12.0, please open a new issue.