Update dependency vitest to v0.34.6 #170

renovate · 2023-08-02T05:39:21Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
vitest (source)	`0.33.0` -> `0.34.6`

Release Notes

vitest-dev/vitest (vitest)

`v0.34.6`

Compare Source

🐞 Bug Fixes

Overwrite global URL with environment's - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/4164 (cbe13)
Correctly resolve external dependencies loaded by custom environments - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/4196 (e3408)
runner: The fixture of test.extend should be init once time in all test - by @Dunqing in https://github.com/vitest-dev/vitest/issues/4168 (730b2)

View changes on GitHub

View changes on GitHub

`v0.34.4`

Compare Source

🐞 Bug Fixes

Resolving dep optimizer issues with workspace - by @thebanjomatic in https://github.com/vitest-dev/vitest/issues/4036 (0c13c)
Don't process config file twice - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/4077 (a84a8)
coverage:
- Log info only when terminal reporter is used - by @AriPerkkio in https://github.com/vitest-dev/vitest/issues/4027 (9f043)
happy-dom:
- Use the nodejs console in happy-dom v11 - by @capricorn86 in https://github.com/vitest-dev/vitest/issues/4090 (59434)
runner:
- Incorrect test name pattern matching - by @Dunqing in https://github.com/vitest-dev/vitest/issues/4071 (b5bf3)
vite-node:
- Check more precisely for root/base paths - by @danielroe in https://github.com/vitest-dev/vitest/issues/4049 (80741)
vitest:
- "vi" doesn't rely on context - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/4031 (0d0f3)
- Only override ssr.optimizer instead of the whole ssr object - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/4080 (410bc)
- Don't start the server when optimizer is enabled - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/4095 (00e81)
- Set SSR env only when transformMode is ssr - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/4083 (f8ea7)
- Show error when calling API on files that user has no access to - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/4085 (8b39c)
web-worker:
- Don't rely on browser API when it's not provided - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/4014 (e78a4)

View changes on GitHub

`v0.34.3`

Compare Source

🚀 Features

coverage: Add allowExternal option - by @vojvodics and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3894 (c03fa)
vitest: Export all reporters in vitest/reporters - by @Dunqing and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3980 (5704b)

🐞 Bug Fixes

Should remove mockPath from callstack whether success or failed - by @miserylee and lijifei in https://github.com/vitest-dev/vitest/issues/3971 (5eb85)
Add workspace config files to default coverage excludes - by @FelixGraf and @AriPerkkio in https://github.com/vitest-dev/vitest/issues/3973 (20263)
Report file error as a on JUnit - by @3c1u in https://github.com/vitest-dev/vitest/issues/3997 (00c43)
jsdom: Correctly resolve buffer on typed arrays - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3998 (b42cf)
ui: Use web hash history in ui - by @segevfiner and @sheremet-va in https://github.com/vitest-dev/vitest/issues/3481 and https://github.com/vitest-dev/vitest/issues/3487 (8caab)
vite-node: Inline HMR types - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3993 (dff60)
vitest: Correctly resolve optimizer status - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3992 (74dc5)

View changes on GitHub

`v0.34.2`

Compare Source

🚀 Features

Allow importing CSS and assets inside external dependencies when using --experimental-vm-threads - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3880 (f4e6e)
vitest: Allow calling ctx.skip() inside the running test - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3966 (5c88d)

🐞 Bug Fixes

Don't bundle utils' source-map entry - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3865 (a08e5)
Reduce the memory consumption when running --experimental-vm-threads - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3872 (d1a08)
Indicator position of error message - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/3855 (3e1e7)
Don't crash when using --experimental-vm-threads, interop CJS default inside node_modules - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3876 (0c53e)
Don't crash if total memory is not supported - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3879 (7d1f8)
Check memory and limit value - by @sheremet-va (f8dfb)
Update module warning as it is moved into server config - by @jellyfishgh in https://github.com/vitest-dev/vitest/issues/3931 (3a3eb)
Define process variable and using import.meta.env together did not work - by @Dunqing in https://github.com/vitest-dev/vitest/issues/3944 (e73ca)
Correctly resolve config in a workspace - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3947 (1c08d)
Don't crash when calling useFakeTimers in VM pool - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3958 (91fe4)
Restrict access to file system via API - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3956 (bcb41)
Typo of mocks plugin name - by @antfu (3073b)
Build not generated execute.d.ts - by @btea in https://github.com/vitest-dev/vitest/issues/3970 (0f8e6)
css:
- Don't mock css-module if ?inline query is specified - by @thebanjomatic and Adam Hines in https://github.com/vitest-dev/vitest/issues/3952 (3891d)
expect:
- Correctly show async matcher diff - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3960 (9423b)
snapshots:
- Update inline snapshot correctly - by @fenghan34 in https://github.com/vitest-dev/vitest/issues/3887 (7b740)
ui:
- Incorrect duration time in vitest ui - by @Dunqing in https://github.com/vitest-dev/vitest/issues/3945 (35139)
- Add support for ui coverage with subdir option - by @userquin in https://github.com/vitest-dev/vitest/issues/3917 (6ecfc)
vitest:
- Use esm module resolution to resolve env - by @danielroe in https://github.com/vitest-dev/vitest/issues/3951 (edb32)
- Allow rewriting process.env.NODE_MODE when using web transform mode - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3957 (eca4b)
- Only consider cwd when using glob - by @g-plane in https://github.com/vitest-dev/vitest/issues/3802 and https://github.com/vitest-dev/vitest/issues/3949 (15b4f)
- Pass environmentOptions to happy-dom integration - by @sheremet-va and Raul de Melo in https://github.com/vitest-dev/vitest/issues/3972 (6a0cb)
web:
- Correctly resolve assets in new URL - by @sheremet-va in https://github.com/vitest-dev/vitest/issues/3950 (a428f)

🏎 Performance

dot-renderer: Speed up getTests - by @gtm-nayan in https://github.com/vitest-dev/vitest/issues/3923 (e9404)

View changes on GitHub

`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.
Custom environment now should be processed before Vitest can consume it. It means that you cannot specify a path to a TS file or use import paths that should be processed by Vite.
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

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate · 2023-08-02T05:39:22Z

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nuxt/[email protected]
npm error Found: [email protected]
npm error node_modules/vitest
npm error   dev vitest@"0.34.6" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional vitest@"^0.30.0 || ^0.31.0 || ^0.32.0 || ^0.33.0" from @nuxt/[email protected]
npm error node_modules/@nuxt/test-utils
npm error   dev @nuxt/test-utils@"3.6.5" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/vitest
npm error   peerOptional vitest@"^0.30.0 || ^0.31.0 || ^0.32.0 || ^0.33.0" from @nuxt/[email protected]
npm error   node_modules/@nuxt/test-utils
npm error     dev @nuxt/test-utils@"3.6.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-07T00_49_41_986Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-07T00_49_41_986Z-debug-0.log

netlify · 2023-08-02T05:40:30Z

❌ Deploy Preview for anohi-no-tweet failed.

Name	Link
🔨 Latest commit	`d052857`
🔍 Latest deploy log	https://app.netlify.com/sites/anohi-no-tweet/deploys/6640847193d26100086cd5ab

renovate · 2024-05-12T08:23:23Z

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @nuxt/[email protected]
npm error Found: [email protected]
npm error node_modules/vitest
npm error   dev vitest@"0.34.6" from the root project
npm error
npm error Could not resolve dependency:
npm error peerOptional vitest@"^0.30.0 || ^0.31.0 || ^0.32.0 || ^0.33.0" from @nuxt/[email protected]
npm error node_modules/@nuxt/test-utils
npm error   dev @nuxt/test-utils@"3.6.5" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/vitest
npm error   peerOptional vitest@"^0.30.0 || ^0.31.0 || ^0.32.0 || ^0.33.0" from @nuxt/[email protected]
npm error   node_modules/@nuxt/test-utils
npm error     dev @nuxt/test-utils@"3.6.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-05-12T08_23_12_839Z-eresolve-report.txt

npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-05-12T08_23_12_839Z-debug-0.log

renovate · 2024-05-12T11:13:37Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

renovate bot added the renovate Created by Renovate label Aug 2, 2023

renovate bot changed the title ~~Update dependency vitest to v0.34.1~~ Update dependency vitest to v0.34.2 Aug 17, 2023

renovate bot force-pushed the renovate/vitest-monorepo branch from e0003cb to abdeff3 Compare August 17, 2023 11:44

renovate bot changed the title ~~Update dependency vitest to v0.34.2~~ Update dependency vitest to v0.34.3 Aug 25, 2023

renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from cfd37c6 to e49a32e Compare August 28, 2023 13:41

renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 98686d6 to 44f9317 Compare September 6, 2023 14:56

renovate bot changed the title ~~Update dependency vitest to v0.34.3~~ Update dependency vitest to v0.34.4 Sep 8, 2023

renovate bot force-pushed the renovate/vitest-monorepo branch 9 times, most recently from 3dc3872 to 8d73586 Compare September 14, 2023 04:49

renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from e9523ba to 1c01b4f Compare September 18, 2023 00:53

renovate bot changed the title ~~Update dependency vitest to v0.34.4~~ Update dependency vitest to v0.34.5 Sep 21, 2023

renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 8c26fe1 to a9be119 Compare September 24, 2023 12:19

renovate bot force-pushed the renovate/vitest-monorepo branch 9 times, most recently from b21eada to f5b5e1c Compare April 14, 2024 12:49

renovate bot force-pushed the renovate/vitest-monorepo branch 10 times, most recently from 77fc096 to 4cc07a4 Compare April 26, 2024 14:18

renovate bot force-pushed the renovate/vitest-monorepo branch 6 times, most recently from 68640ab to 1951ae5 Compare May 7, 2024 00:49

Update dependency vitest to v0.34.6

ed0295a

renovate bot force-pushed the renovate/vitest-monorepo branch from 1951ae5 to ed0295a Compare May 12, 2024 08:23

Update lock file

d052857

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update dependency vitest to v0.34.6 #170

Update dependency vitest to v0.34.6 #170

renovate bot commented Aug 2, 2023 •

edited

Loading

renovate bot commented Aug 2, 2023 •

edited

Loading

netlify bot commented Aug 2, 2023 •

edited

Loading

renovate bot commented May 12, 2024

renovate bot commented May 12, 2024

Update dependency vitest to v0.34.6 #170

Are you sure you want to change the base?

Update dependency vitest to v0.34.6 #170

Conversation

renovate bot commented Aug 2, 2023 • edited Loading

Release Notes

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🏎 Performance

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🚀 Features

🐞 Bug Fixes

🏎 Performance

🐞 Bug Fixes

🚨 Breaking Changes

🚀 Features

🐞 Bug Fixes

🏎 Performance

Configuration

renovate bot commented Aug 2, 2023 • edited Loading

⚠ Artifact update problem

File name: package-lock.json

netlify bot commented Aug 2, 2023 • edited Loading

❌ Deploy Preview for anohi-no-tweet failed.

renovate bot commented May 12, 2024

⚠️ Artifact update problem

File name: package-lock.json

renovate bot commented May 12, 2024

Edited/Blocked Notification

renovate bot commented Aug 2, 2023 •

edited

Loading

renovate bot commented Aug 2, 2023 •

edited

Loading

netlify bot commented Aug 2, 2023 •

edited

Loading