Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency vitest to v0.34.6 #51

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 28, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) 0.23.4 -> 0.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
   🚀 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 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.
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.4

Compare Source

   🚀 Features

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 was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title Update dependency vitest to v0.24.3 Update dependency vitest to v0.24.4 Oct 31, 2022
@renovate renovate bot changed the title Update dependency vitest to v0.24.4 Update dependency vitest to v0.24.5 Nov 1, 2022
@renovate renovate bot changed the title Update dependency vitest to v0.24.5 Update dependency vitest to v0.25.0 Nov 7, 2022
@renovate renovate bot changed the title Update dependency vitest to v0.25.0 Update dependency vitest to v0.25.1 Nov 8, 2022
@renovate renovate bot changed the title Update dependency vitest to v0.25.1 Update dependency vitest to v0.25.2 Nov 14, 2022
@renovate renovate bot changed the title Update dependency vitest to v0.25.2 Update dependency vitest to v0.25.3 Nov 22, 2022
@renovate renovate bot changed the title Update dependency vitest to v0.25.3 Update dependency vitest to v0.29.3 Mar 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 3e16ae3 to 38a9cea Compare March 20, 2023 02:50
@renovate renovate bot changed the title Update dependency vitest to v0.29.3 Update dependency vitest to v0.29.5 Mar 20, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 354e3ad to c870a9c Compare March 20, 2023 20:48
@renovate renovate bot changed the title Update dependency vitest to v0.29.5 Update dependency vitest to v0.29.7 Mar 20, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from c870a9c to 11e884d Compare March 28, 2023 13:28
@renovate renovate bot changed the title Update dependency vitest to v0.29.7 Update dependency vitest to v0.29.8 Mar 28, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 00b9815 to 417b0c2 Compare April 9, 2023 15:26
@renovate renovate bot changed the title Update dependency vitest to v0.29.8 Update dependency vitest to v0.30.0 Apr 9, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from de870ab to 1bcc2ed Compare April 11, 2023 13:09
@renovate renovate bot changed the title Update dependency vitest to v0.30.0 Update dependency vitest to v0.30.1 Apr 11, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 8067f11 to 5301976 Compare June 1, 2023 17:22
@renovate renovate bot changed the title Update dependency vitest to v0.31.1 Update dependency vitest to v0.31.4 Jun 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 5301976 to 4de8d61 Compare June 6, 2023 17:48
@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-monorepo branch from 4de8d61 to 2e10920 Compare June 16, 2023 14:04
@renovate renovate bot changed the title Update dependency vitest to v0.32.0 Update dependency vitest to v0.32.1 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 2e10920 to 19ff9a3 Compare June 16, 2023 20:10
@renovate renovate bot changed the title Update dependency vitest to v0.32.1 Update dependency vitest to v0.32.2 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 19ff9a3 to 56f80f0 Compare July 3, 2023 11:44
@renovate renovate bot changed the title Update dependency vitest to v0.32.2 Update dependency vitest to v0.32.4 Jul 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 56f80f0 to 8cbafcd Compare July 6, 2023 17:09
@renovate renovate bot changed the title Update dependency vitest to v0.32.4 Update dependency vitest to v0.33.0 Jul 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from 8a73c19 to 370b7a9 Compare July 19, 2023 00:39
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 370b7a9 to 54b28c0 Compare August 1, 2023 17:38
@renovate renovate bot changed the title Update dependency vitest to v0.33.0 Update dependency vitest to v0.34.1 Aug 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 54b28c0 to bd0f86a Compare August 17, 2023 10:33
@renovate renovate bot changed the title Update dependency vitest to v0.34.1 Update dependency vitest to v0.34.2 Aug 17, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from bd0f86a to e56b915 Compare August 25, 2023 08:52
@renovate renovate bot changed the title Update dependency vitest to v0.34.2 Update dependency vitest to v0.34.3 Aug 25, 2023
@renovate renovate bot changed the title Update dependency vitest to v0.34.3 chore(deps): update dependency vitest to v0.34.3 Aug 31, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e56b915 to 2fac230 Compare August 31, 2023 08:03
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.3 chore(deps): update dependency vitest to v0.34.4 Sep 8, 2023
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.4 chore(deps): update dependency vitest to v0.34.5 Sep 21, 2023
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.5 chore(deps): update dependency vitest to v0.34.6 Sep 29, 2023
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