Skip to content

Update dependency vitest to v0.34.6#30

Open
renovate[bot] wants to merge 1 commit intodependency-updatesfrom
renovate/vitest-0.x
Open

Update dependency vitest to v0.34.6#30
renovate[bot] wants to merge 1 commit intodependency-updatesfrom
renovate/vitest-0.x

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Apr 25, 2022

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) 0.9.40.34.6 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

v0.34.6

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.34.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.34.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.34.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.34.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v0.34.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.34.0

Compare Source

   🚨 Breaking Changes
  • Transform mode affects only test files, not regular files  -  by @​sheremet-va in #​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 #​3615 (0c6f6)
  • Remove @vitest/coverage-c8 package  -  by @​AriPerkkio in #​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 #​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 #​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 #​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 #​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
   🐞 Bug Fixes
   🏎 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
    View changes on GitHub

v0.32.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.32.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.32.0

Compare Source

   🚨 Breaking Changes
  • Throw an error, if the module cannot be resolved  -  by @​sheremet-va in #​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 #​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 #​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 #​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.
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.2

Compare Source

   🚀 Features
   🐞 Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/vitest-0.x branch 2 times, most recently from ef5fe82 to 515ff19 Compare May 2, 2022 17:57
@renovate renovate bot changed the title Update dependency vitest to v0.10.0 Update dependency vitest to v0.10.1 May 2, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 515ff19 to b630bc5 Compare May 3, 2022 09:57
@renovate renovate bot changed the title Update dependency vitest to v0.10.1 Update dependency vitest to v0.10.2 May 3, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from b630bc5 to 73dbaba Compare May 5, 2022 18:40
@renovate renovate bot changed the title Update dependency vitest to v0.10.2 Update dependency vitest to v0.10.4 May 5, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 73dbaba to 24ecbd7 Compare May 6, 2022 12:36
@renovate renovate bot changed the title Update dependency vitest to v0.10.4 Update dependency vitest to v0.10.5 May 6, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 24ecbd7 to 0321380 Compare May 7, 2022 23:51
@renovate renovate bot changed the title Update dependency vitest to v0.10.5 Update dependency vitest to v0.11.0 May 7, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 0321380 to ab7041e Compare May 8, 2022 10:31
@renovate renovate bot changed the title Update dependency vitest to v0.11.0 Update dependency vitest to v0.12.0 May 8, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from ab7041e to 8cfd48c Compare May 9, 2022 11:19
@renovate renovate bot changed the title Update dependency vitest to v0.12.0 Update dependency vitest to v0.12.1 May 9, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 8cfd48c to 32c97ca Compare May 9, 2022 17:20
@renovate renovate bot changed the title Update dependency vitest to v0.12.1 Update dependency vitest to v0.12.2 May 9, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 32c97ca to b6e0397 Compare May 10, 2022 02:14
@renovate renovate bot changed the title Update dependency vitest to v0.12.2 Update dependency vitest to v0.12.3 May 10, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from b6e0397 to 709ef8d Compare May 11, 2022 00:56
@renovate renovate bot changed the title Update dependency vitest to v0.12.3 Update dependency vitest to v0.12.4 May 11, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 709ef8d to fa6528e Compare May 13, 2022 14:44
@renovate renovate bot changed the title Update dependency vitest to v0.12.4 Update dependency vitest to v0.12.5 May 13, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from fa6528e to bb5f9b6 Compare May 13, 2022 17:35
@renovate renovate bot changed the title Update dependency vitest to v0.12.5 Update dependency vitest to v0.12.6 May 13, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from bb5f9b6 to b3220d3 Compare May 20, 2022 11:32
@renovate renovate bot changed the title Update dependency vitest to v0.12.6 Update dependency vitest to v0.12.7 May 20, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from b3220d3 to c80fc14 Compare May 21, 2022 12:01
@renovate renovate bot changed the title Update dependency vitest to v0.12.7 Update dependency vitest to v0.12.8 May 21, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from c80fc14 to ef31b48 Compare May 21, 2022 19:33
@renovate renovate bot changed the title Update dependency vitest to v0.14.2 Update dependency vitest to v0.15.0 Jun 14, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from e00fbf2 to 249bacd Compare June 15, 2022 13:04
@renovate renovate bot changed the title Update dependency vitest to v0.15.0 Update dependency vitest to v0.15.1 Jun 15, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 249bacd to 128fda6 Compare June 21, 2022 12:12
@renovate renovate bot changed the title Update dependency vitest to v0.15.1 Update dependency vitest to v0.15.2 Jun 21, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 128fda6 to b962953 Compare June 24, 2022 14:23
@renovate renovate bot changed the title Update dependency vitest to v0.15.2 Update dependency vitest to v0.16.0 Jun 24, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from b962953 to dff7edd Compare September 25, 2022 14:08
@renovate renovate bot changed the title Update dependency vitest to v0.16.0 Update dependency vitest to v0.23.4 Sep 25, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from dff7edd to 6dd658f Compare November 20, 2022 21:13
@renovate renovate bot changed the title Update dependency vitest to v0.23.4 Update dependency vitest to v0.25.2 Nov 20, 2022
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 6dd658f to ee83fdb Compare March 12, 2023 04:42
@renovate renovate bot changed the title Update dependency vitest to v0.25.2 Update dependency vitest to v0.29.2 Mar 12, 2023
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from ee83fdb to 4b26ed5 Compare March 16, 2023 23:44
@renovate renovate bot changed the title Update dependency vitest to v0.29.2 Update dependency vitest to v0.29.3 Mar 16, 2023
@renovate renovate bot changed the title Update dependency vitest to v0.29.3 Update dependency vitest to v0.29.7 Mar 27, 2023
@renovate renovate bot force-pushed the renovate/vitest-0.x branch 2 times, most recently from 62b1e6c to 7fe74e8 Compare March 29, 2023 21:57
@renovate renovate bot changed the title Update dependency vitest to v0.29.7 Update dependency vitest to v0.29.8 Mar 29, 2023
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 7fe74e8 to 8ddb856 Compare April 17, 2023 10:42
@renovate renovate bot changed the title Update dependency vitest to v0.29.8 Update dependency vitest to v0.30.1 Apr 17, 2023
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 8ddb856 to 81c19aa Compare June 1, 2023 03:57
@renovate renovate bot changed the title Update dependency vitest to v0.30.1 Update dependency vitest to v0.31.3 Jun 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 81c19aa to d7c2b0c Compare June 1, 2023 10:56
@renovate renovate bot changed the title Update dependency vitest to v0.31.3 Update dependency vitest to v0.31.4 Jun 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from d7c2b0c to 6d203d9 Compare June 6, 2023 19:46
@renovate renovate bot changed the title Update dependency vitest to v0.31.4 Update dependency vitest to v0.32.0 Jun 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-0.x branch from 6d203d9 to 076d46f Compare June 16, 2023 14:53
@renovate
Copy link
Contributor Author

renovate bot commented Dec 8, 2024

Autoclosing Skipped

This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants