Upgrade @vue/test-utils: 1.1.2 → 1.3.0 (minor)

[depfu]

Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ @​vue/test-utils (1.1.2 → 1.3.0) · Repo · Changelog

Release Notes

1.3.0

1.3.0 is a small release, in terms of code changes, but brings back a popular feature that was previously deprecated: chaining for CSS selectors in getComponent and findComponent. This also is ported to Test Utils v2, so you can enjoy largely the same API in both libraries.

Features

feat: restore chaining and CSS selectors for findComponent (#1910)

Fixes

fix: verify object not null for typeof (#1897)
fix(types): Remove argument for resetAutoDestroyState (#1907)

1.2.2

This release contains no bug fixes or behavior changes; it simply improves the type definitions.

Types

• types: type createLocalVue method #1873
• types: add generic for wrapper.find() and wrapper.get() #1871

1.2.1

This is a small release with just two minor bug fixes.

Fixes

• fix #1845: add functional component check in component name match (#1857)
• updated router link stub to match actual router-link interface (#1840)

1.2.0

Features

• feat(stubs): render function props deterministically (#1834). Note: this may break some snapshots of shallow mounted functional components.

Fixes

• fix: correctly find functional components (#1835)
• fix: trigger keyboard event regression (#1826)

1.1.4

Feat

• export ErrorWrapper #1814

Fixes

• trigger('focus') added natural to jsdom behavior (#1777)
• fix max range stack size (f#1768)
• VTU don't return key property to event when use trigger.('eventName.key') #1808
• allow find stubbed functional component by name (#1817)

Types

• add type definitions for ExtendedVue (#1789)

1.1.3

Fixes

• do not console.error handled exceptions (#1761) @marcgibbons

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)