[Snyk] Upgrade @vue/test-utils from 1.3.0 to 2.4.6 #166
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![snyk-io[bot]](https://avatars.githubusercontent.com/in/372950?s=60&v=4){kind=small}
Snyk has created this PR to upgrade @vue/test-utils from 1.3.0 to 2.4.6. See this package in npm: @vue/test-utils See this project in Snyk: https://app.snyk.io/org/cachiman/project/a49b2236-259f-4147-af11-1f39ed2c4f32?utm_source=github-cloud-app&utm_medium=referral&page=upgrade-pr
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR was automatically created by Snyk using the credentials of a real user.
Snyk has created this PR to upgrade @vue/test-utils from 1.3.0 to 2.4.6.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
The recommended version is 80 versions ahead of your current version.
The recommended version was released on 2 months ago.
Release notes
Package name: @vue/test-utils
What's Changed
New Contributors
Full Changelog: v2.4.5...v2.4.6
What's Changed
New Contributors
Full Changelog: v2.4.4...v2.4.5
What's Changed
New Contributors
Full Changelog: v2.4.3...v2.4.4
What's Changed
Full Changelog: v2.4.2...v2.4.3
What's Changed
Note: A fix for the
text()method (#2231) may force developers to update tests that were checking the text of several elements at once, as the spaces of each element are now trimmed (as they are when usingtext()on a single element). So if you were checking the text of<span>Trimmed </span><span>Example</span>, it is nowTrimmedExampleinstead ofTrimmed Example(and thetext()of the first span is stillTrimmedas it was before).Fix
<transition>stubs by @ alecgibson in #2185setDataby @ rory-instil in #2166VNodeChildtype fromvueto avoid breakage by @ sodatea in #2237Docs
Chore
New Contributors
Full Changelog: v2.4.1...v2.4.2
What's Changed
Fixes
Docs
isVisible()by @ alecgibson in #2122(Dev) Dependencies
New Contributors
Full Changelog: v2.4.0...v2.4.1
Note: there might be some minor breaking changes around types. We tried hard to avoid this and tested a few different projects, but there was some major under the hood changes relating to types (which should improve the TypeScript experience). See the note at the top of the previous release, 2.4.0-alpha.2: https://github.com/vuejs/test-utils/releases/tag/v2.4.0-alpha.2
Between the last main release, v2.3.2, and v2.4.0, there were three alphas:
Please see those release notes for changes if you are updating from v2.3.2. Again, there should not be any major changes, and you code and tests should continue to work as before without any changes.
If you do encounter breaking changes transitioning from 2.3.x -> 2.4.x, please file an issue.
Note: It has no API related breaking changes, but some types might be impacted - the full extent of #2026 is still being investigated, but at this point it's unlikely you'll need to change any code. In general, type safety should be improved across the board.
What's Changed