Update dependency @vitest/coverage-istanbul to v0.29.3 - autoclosed
This MR contains the following updates:
Package | Change | Age | Adoption | Passing | Confidence |
---|---|---|---|---|---|
@vitest/coverage-istanbul | 0.28.2 -> 0.29.3 |
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the logs for more information.
Release Notes
vitest-dev/vitest
v0.29.3
🚀 Features
- Use custom colors implementation instead of picocolors - by @sheremet-va (427b0)
- Uncaught errors to indicate env teardown - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2982 (1fe82)
- config: Add an option to run setupFiles in sequence - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3008 (c2e25)
🐞 Bug Fixes
- Console log not visible - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2943 (02808)
- Remove duplicate execArgv when deps.registerNodeLoader: true - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2965 (a1954)
- Prevent running test cases timers after environment teardown - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2971 (bde75)
- Don't mark setupFiles as test files, if experimentaOptimizer is used - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2974 (819c6)
- Config errors not visible - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2995 (f01c7)
- --inspect to work inside workers - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2983 (36087)
-
types: Use
any
as default value for TArgs in vi.fn() - by @jessevanassen in https://github.com/vitest-dev/vitest/issues/2947 (1bdcc)
🏎 Performance
- reporters: Overall improvements - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3006 (22ca0)
View changes on GitHub
v0.29.2
🐞 Bug Fixes
- Optimize dependencies in setup files - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2935 (c169f)
- coverage: C8 provider to work when isolate:false - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2929 (86538)
View changes on GitHub
v0.29.1
🐞 Bug Fixes
- Wait for optimized dependency to be bundled in non-pnpm package managers - by @sheremet-va (d2460)
View changes on GitHub
v0.29.0
This release makes some significant changes to how tests are running. If you were using --no-threads
before, you might consider enabling --single-thread
instead (because your tests are now running in child_process
instead of a worker thread) or try our new performance optimization feature (discussed later). If you were relying on API that was not available inside a worker (like process.chdir()
, you can now use this option.
One of the potential breaking bug fixes is that environments do not share the same global scope anymore if you run them with --no-isolate
, --no-threads
or --single-thread
- you might need to update your setup files if you were relying on a global variable before.
If you had performance issues on large code bases before, try the new deps.experimentalOptimizer
option instead of disabling threads. Feedback is welcome!
One of the breaking changes includes adding a link to snapshots inside snapshot files, meaning you will need to update all your snapshots.
🚨 Breaking Changes
- Vitest as peer dependency for coverage packages - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2836 (94247)
- Coverage-c8 to use V8 profiler directly instead of
NODE_V8_COVERAGE
- by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2786 (095c6) - Add a link to the comment at the top of the snapshot file - by @btea in https://github.com/vitest-dev/vitest/issues/2867 (615e1)
- Always run separate environments in isolation - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2860 (1f858)
- Tests with
node
andjsdom
(and other environments) now don't share the same global scope, if you run them with--no-isolate
or--no-threads
flag. Vitest doesn't provide a way to restore the previous behavior as it is considered a bug.
- Tests with
- Use child_process when --no-threads is used - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2772 (7bf54)
- Tests inside
chid_process
might run longer due to the communication overhead. If you want to restore the previous behavior, use--single-thread
.
- Tests inside
🚀 Features
- Add test seed to banner - by @btkostner in https://github.com/vitest-dev/vitest/issues/2877 (bdb39)
- Use custom source-map-support implementation - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2905 (6ff6c)
- Add an option to enable Vite optimizer - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2912 (af8de)
-
coverage:
- Add support for coverage reporter options - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2690 (f8176)
- Automatic threshold updating - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2886 (e1652)
-
spy:
- Implement mock.withImplementation API - by @obadakhalili and @sheremet-va in https://github.com/vitest-dev/vitest/issues/2835 (610b1)
-
vite-node:
- Cli option for vite mode - by @abarke in https://github.com/vitest-dev/vitest/issues/2893 (0fc08)
🐞 Bug Fixes
- Wait for console.log to print a message before terminating a worker - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2861 (fbc54)
- Cleanup last mocked cache when call vi.doMock - by @mysteryven in https://github.com/vitest-dev/vitest/issues/2872 (65d71)
- Reload changed configuration file on watch mode - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2889 (4d277)
- coverage: Custom providers to work inside worker threads - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2817 (81604)
View changes on GitHub
v0.28.5
🚀 Features
- Add --script option to vite-node - by @jgoux and @dammy001 in https://github.com/vitest-dev/vitest/issues/2793 (d3d6b)
- Inject executor directly into runner - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2858 (62c43)
🐞 Bug Fixes
- Don't call "afterAll" hooks, if suite was skipped - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2802 (aa1aa)
- Always display serialized error, even if it doesn't have stack - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2829 (ab5f8)
- Clear mocks between tests - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2857 (c420c)
-
expect:
- Check for no 'throw' type in toHaveReturned - by @trivikr in https://github.com/vitest-dev/vitest/issues/2850 (1164c)
- Accept array index as number in toHaveProperty - by @trivikr in https://github.com/vitest-dev/vitest/issues/2808 (8705e)
🏎 Performance
- Don't inline Vitest entry - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2819 (570c6)
View changes on GitHub
v0.28.4
🐞 Bug Fixes
- Setup correct utils inside asymmetric matchers - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2768 (415c8)
- Cjs exports has Object.prototype instead of null - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2769 (4fc49)
- Duplicate callbacks in vite-node HMR - by @jgoux in https://github.com/vitest-dev/vitest/issues/2792 (f0333)
- Do not include source files in
onWatcherStart
whentypecheck.ignoreSourceErrors
is true - by @mascii and @sheremet-va in https://github.com/vitest-dev/vitest/issues/2774 (d612e)
View changes on GitHub
v0.28.3
🚀 Features
- Allow using atomics to communicate between threads - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2758 (3679c)
- Show active filename pattern on CLI - by @AriPerkkio (a0455)
- Show active test name pattern on CLI - by @AriPerkkio (df7c4)
- Allow
config
option to be false - by @antfu in https://github.com/vitest-dev/vitest/issues/2749 (c66e3)
🐞 Bug Fixes
- Watch mode's filename pattern to persist on unrelated file changes - by @AriPerkkio (712ac)
- Watch mode's filename pattern to persist re-run of failed tests, snapshot updates and testname filter changes - by @AriPerkkio (1c65a)
- Dont incorrectly mark run failed if filename pattern excludes previously failed tests - by @AriPerkkio (61cf9)
- coverage: Istanbul crashes when no tests were run - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/2753 (ebc95)
🏎 Performance
- Don't import vite in worker - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/2759 (e49c1)
View changes on GitHub
Configuration
-
If you want to rebase/retry this MR, check this box
This MR has been generated by Renovate Bot.