chore: update npm/vue to use latest test utils #26633
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
script setup
component are not accessible on the component instance (AKAwrapper.vm
) #26575Additional details
Just updated the underlying
vue/test-utils
dependency to get some of the latest features, specifically, access variables declared and exposed viadefineExpose
.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 theexternal
key in the rollup config. If you docd 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
cypress-documentation
?type definitions
?