Update dependency @vitest/coverage-istanbul to ^0.34.0 (!311) · Merge requests · Platform One / Party Bus / Launchboard / launchboard-fe

renovate requested to merge renovate/vitest-coverage-istanbul-0.x into master Aug 10, 2023

This MR contains the following updates:

Package	Type	Update	Change
@vitest/coverage-istanbul (source)	devDependencies	minor	`^0.31.1` -> `^0.34.0`

⚠ Dependency Lookup Warnings ⚠

Warnings were logged while processing this repo. Please check the logs for more information.

Release Notes

vitest-dev/vitest

`v0.34.1`

Compare Source

🐞 Bug Fixes

Pass --experimental-vm-worker-memory-limit to tinypool - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3856 (3c67a)

View changes on GitHub

`v0.34.0`

Compare Source

🚨 Breaking Changes

Transform mode affects only test files, not regular files - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3491 (9608b)
- transformMode is now moved to server.transformMode. This option is highly discouraged to use. If you need to change the transform mode, use the new option testTransformMode instead to control the mode based on the running test, not the current file path. By default, tests with jsdom or happy-dom use web transform mode, and tests using node or edge environment use ssr mode. If you have a custom environment, it should provide transformMode property.
Disable coverage.reportOnFailure by default - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3615 (0c6f6)
Remove @vitest/coverage-c8 package - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3614 (a90d6)
- @vitest/coverage-c8 is no longer supported. Please, use @vitest/coverage-v8 instead.
Support running tests using VM context - by @sheremet-va and @dammy001 in https://github.com/vitest-dev/vitest/issues/3203 (b0929)
- To address speed issues in some applications, Vitest now provides experimentalVmThreads pool to run your tests using VM Sandboxes environment. Make sure you understand all pitfalls of this pool before opening an issue.
Introduce server option - by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3725 (dc4fa)
- Most of deps. options are now moved to server.deps with a deprecation warning. Please, consider using deps.optimizer instead of deps.inline/deps.external. Ideally, we would like to move away from using server.deps.inline altogether.
vite-node: Make CLI arguments parsing behavior consistent with node/tsx/ts-node - by @rxliuli in https://github.com/vitest-dev/vitest/issues/3574 (1cd4e)
- You now have to provide CLI arguments before the entry point. For example, instead of vite-node index.ts --watch, you now have to do vite-node --watch index.ts.
Add preact example, remove optimizer experimental status, enable by default - by @sheremet-va and @eryue0220 in https://github.com/vitest-dev/vitest/issues/3854 (4b946)
- deps.optimizer is now enabled by default. This means that Vitest will bundle specified dependencies before running your tests. This field inherits options from optimizeDeps and ssr.optimizeDeps which are populated by other plugins (like, Svelte).

🚀 Features

Support describe.sequential - by @fenghan34 and @dammy001 in https://github.com/vitest-dev/vitest/issues/3771 (86934)
Support config junit reporter className with env - by @InfiniteXyy in https://github.com/vitest-dev/vitest/issues/3808 (e8bc4)
Running vitest with --related --watch reruns non-affected tests if they were changed during a run - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3844 (c9aea)

🐞 Bug Fixes

Isolate workers between envs and workspaces - by @AriPerkkio (ed4e0)
Modify condition - by @btea (a78e6)
Module Graph view is blocking the Console view - by @g4rry420 (3b5f9)
Port the latest defineConfig type from vite - by @sodatea in https://github.com/vitest-dev/vitest/issues/3804 (9c8e3)
Don't overwrite Node.js URL global - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3828 (cdab4)
ForceRerunTriggers correctly triggers a rerun - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3829 (17988)
browser:
- Don't inline magic-string and estree-walker - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3726 (ee937)
- Multi-suite coverage - by @elby22 in https://github.com/vitest-dev/vitest/issues/3806 (5de9a)
core:
- DataView comparison does not work in toStrictEqual - by @Dunqing (52aef)
coverage:
- V8 provider to pick source maps without url query params - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3784 (280e6)
- Update istanbul-lib-instrument to v6 to fix vulnerable dependency - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3814 (f3bd9)
- Exclude vite virtual modules by default - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3794 (3c851)
node:
- Guard error info - by @btea (88b39)
vite-node:
- Always treat node_modules as modulesDirectory - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3830 (51ab8)
- Normalize drive letter to keep the same reference to a module - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3836 (45521)
- Correctly resolve hmr filepath - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3834 (711a6)
watch:
- Clear screen on all terminals - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3661 (8bd26)

🏎 Performance

Deprecate deps.registerNodeLoader - by @sheremet-va (7f45b)
- This option was introduced to support aliasing inside external packages. Please, use deps.optimizer.web instead. If you test Node.js applications, consider adding external packages to server.deps.inline.

View changes on GitHub

`v0.33.0`

Compare Source

🚨 Breaking Changes

Revert default include patterns - by @so1ve #3729
- 0.32.0 changed the default include globs to be compatible with Jest. After a discussion with the community, we are reverting this change because it turned out to be non-intuitive.

🐞 Bug Fixes

Add missing JSDom living keys - by @DerZade in https://github.com/vitest-dev/vitest/issues/3702 (83a86)
vite-node:
- Don't fail when importing Promise module - by @sheremet-va (08192)
- Allow importing node:test - by @sheremet-va (db22c)

View changes on GitHub

`v0.32.4`

Compare Source

🐞 Bug Fixes

browser: Correctly optimize CJS dependencies - by @sheremet-va (3d090)

View changes on GitHub

View changes on GitHub

`v0.32.2`

Compare Source

🐞 Bug Fixes

browser: Don't fail on importing diff-sequences - by @sheremet-va (00b0e)

View changes on GitHub

`v0.32.1`

Compare Source

🚀 Features

Export registerConsoleShortcuts from vitest/node - by @deot in https://github.com/vitest-dev/vitest/issues/3563 (bc49b)
expect: Support expect.unreachable - by @fenghan34 and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3556 (8e385)
runner: describe/test name support anonymous function - by @btea in https://github.com/vitest-dev/vitest/issues/3562 (3d436)

🐞 Bug Fixes

Avoid call stack recursion with large error (fix: #3060) - by @nathanmmiller and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3078 and https://github.com/vitest-dev/vitest/issues/3060 (02196)
Automatically remove define related configuration - by @btea in https://github.com/vitest-dev/vitest/issues/3552 (368b8)
Import performance from perf_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)
Revert concordance diff, use jest's diff output - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3582 (9c7ea)
Typo in config suggestion - by @Krisell in https://github.com/vitest-dev/vitest/issues/3583 (68985)
browser:
- Change optimized deps to use vitest - by @userquin in https://github.com/vitest-dev/vitest/issues/3580 (b4ac8)
- Access vi_inject only if it was injected - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3587 (d9e14)
mocker:
- Respect namespace import when hoisting vi.mock - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3547 (158c4)
ui:
- Navigate to dashboard when re-running tests from coverage page - by @userquin in https://github.com/vitest-dev/vitest/issues/3529 (bc283)
vite-node:
- Correctly resolve virtual modules - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3544 (0cbb0)
- Fix errors caused by commonjs export circular references - by @rxliuli in https://github.com/vitest-dev/vitest/issues/3570 (b097c)

View changes on GitHub

`v0.32.0`

Compare Source

🚨 Breaking Changes

Throw an error, if the module cannot be resolved - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3307 (1ad63)
- 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.
Improve globs - by @nickmccurdy in https://github.com/vitest-dev/vitest/issues/3392 (19ecc)
- 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.
Add @vitest/coverage-v8 package - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3339 (82112)
- 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.
mocker: Don't restore mock to the original if the module is automocked - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3518 (c1004)
- spy.mockRestore on auto-mocked named exports will no longer restore their implementation to the actual function. This behavior better matches what Jest does.