This repository was archived by the owner on Dec 22, 2024. It is now read-only.
chore(deps): update dependency vitest to v0.10.0 #18
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 contains the following updates:
^0.9.4
->0.10.0
Release Notes
vitest-dev/vitest
v0.10.0
Compare Source
Breaking Changes
From Vitest v0.10.0, the callback style of declaring tests is deprecated. You can rewrite them to use
async
/await
functions, or use Promise to mimic the callback style.Features
beforeAll
/beforeEach
cleanup callbackbeforeAll
/beforeEach
now accepts an optional cleanup function as the return value (equivalent toafterAll
/afterEach
).Learn more at:
beforeAll
beforeEach
Test Context
Inspired by Playwright Fixtures, Vitest's test context allows you to define utils, states, and fixtures that can be used in your tests.
Learn more at Test Context
Concurrent Snapshot
Due to the limitation of JavaScript, timing based Singleton pattern will cause conflicts when running multiple async functions in concurrent. Previously reported as #551. Thanks to the newly introduced Test Context, we can now provide a test specific
expect
instance to avoid conflicts. To use it, you can destructure theexpect
from each test context instead of the global one.Reporter from file / package
Now you can pass a path to file, or a package name to the
reporters
options to use custom reporter. Thanks to @ericjgagnon (#1136) (f2bceb2)Bug Fixes
Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.