You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vitest used to fall back to the original import when it could not resolve it to the file path or the virtual module. This leads to hard-to-find module graph mismatches if you had incorrect alias or relied on relative imports to be resolved to the project root (which is usual behavior in TypeScript) because the code accidentally "worked". With this release, Vitest will now throw an error if it cannot resolve the module - there are possible edge cases that are not covered yet, so if you have any problems with this, please open a separate issue with reproduction.
Vitest now has glob patterns similar to Jest for better compatibility. It's possible that some files will be considered test files when previously they were not. For example, Vitest now considers test.js to be a test file. Also any file in __tests__ is now considered to be a test, not just files with test or spec suffix.
Vitest now uses v8 code coverage directly for better performance. @vitest/coverage-c8 is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user has c8 as their coverage provider. Please, install the new @vitest/coverage-v8 package if you previously used @vitest/coverage-c8.
spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.
This file contains hidden or 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
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.30.1->^0.32.0Release Notes
vitest-dev/vitest
v0.32.2Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.32.1Compare Source
🚀 Features
registerConsoleShortcutsfromvitest/node- by @deot in https://github.com/vitest-dev/vitest/issues/3563 (bc49b)expect.unreachable- by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3556 (8e385)describe/testname support anonymous function - by @btea in https://github.com/vitest-dev/vitest/issues/3562 (3d436)🐞 Bug Fixes
performancefromperf_hooks- by @Max10240 and wangbaolong.wbl in https://github.com/vitest-dev/vitest/issues/3578 and https://github.com/vitest-dev/vitest/issues/3579 (24ec8)vitest- by @userquin in https://github.com/vitest-dev/vitest/issues/3580 (b4ac8)View changes on GitHub
v0.32.0Compare Source
🚨 Breaking Changes
test.jsto be a test file. Also any file in__tests__is now considered to be a test, not just files withtestorspecsuffix.@vitest/coverage-v8package - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3339 (82112)@vitest/coverage-c8is deprecated as Vitest no longer uses c8 package for coverage output. It will not be updated anymore, and Vitest will fail in the next version if the user hasc8as their coverage provider. Please, install the new@vitest/coverage-v8package if you previously used@vitest/coverage-c8.spy.mockRestoreon auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.🚀 Features
expect.soft- by @Dunqing in https://github.com/vitest-dev/vitest/issues/3507 (7c687)describe/testname - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/3497 (15253)🐞 Bug Fixes
View changes on GitHub
v0.31.4Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
v0.31.3Compare Source
🚀 Features
VITE_NODE_DEPS_MODULE_DIRECTORIESfrom .npmrc - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3471 (393bf)🐞 Bug Fixes
View changes on GitHub
v0.31.2Compare Source
🚀 Features
test.eachordescribe.each- by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3360 (7c2f7)reportOnFailureoption - by @AriPerkkio and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3453 (1988f)🐞 Bug Fixes
SIGINTis received - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3407 (a2cc2)rejects&resolvesbreaks with thenable objects - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/3456 (4e996)birpctimeouts whenMath.randommock is not restored - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3460 (cd5d5)lessextension - by @rluvaton in https://github.com/vitest-dev/vitest/issues/3465 (4d045)PartialMockwith async TReturns - by @ghry5 in https://github.com/vitest-dev/vitest/issues/3462 (b664d)View changes on GitHub
v0.31.1Compare Source
🚀 Features
rshould rerun current pattern tests - by @Dunqing and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3305 (69d27)🐞 Bug Fixes
cwdfrom test name filter - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3353 (324a9)toMatchInlineSnapshotfails when file path includes parentheses - by @pacexy in https://github.com/vitest-dev/vitest/issues/3370 and https://github.com/vitest-dev/vitest/issues/3371 (dcf13)View changes on GitHub
v0.31.0Compare Source
🚨 Breaking Changes
Remove
browserfrom allowed pools insidepoolMatchGlobconfig option. Please, use Vitest workspaces for running tests in the browser.Move assertion declarations to expect package - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3294 (cf3af)
🚀 Features
vi.hoistedto run code before imports are executed:vi.mock:--bailoption for cancelling test run - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3163 (8d460)🐞 Bug Fixes
thresholdAutoUpdateto work withperFile- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3182 (29eeb)import.meta.hot.sendmock - by @antfu (b1624)View changes on GitHub
Configuration
📅 Schedule: Branch creation - "after 9pm on sunday" (UTC), Automerge - 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 Mend Renovate. View repository job log here.