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.3 - autoclosed #1977

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 17, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest 0.31.1 -> 0.34.3 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

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
   🐞 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
    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.


Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest 0.31.1 -> 0.34.3 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

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
   🐞 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
    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 renovate bot changed the title chore(deps): update dependency vitest to v0.31.1 chore(deps): update dependency vitest to v0.31.1 - autoclosed May 27, 2023
@renovate renovate bot closed this May 27, 2023
@renovate renovate bot deleted the renovate/vitest-monorepo branch May 27, 2023 16:07
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.31.1 - autoclosed chore(deps): update dependency vitest to v0.31.1 May 30, 2023
@renovate renovate bot reopened this May 30, 2023
@renovate renovate bot restored the renovate/vitest-monorepo branch May 30, 2023 13:15
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.31.1 chore(deps): update dependency vitest to v0.31.2 May 30, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 429a6fb to b4bdbbd Compare May 30, 2023 15:52
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.31.2 chore(deps): update dependency vitest to v0.31.3 May 31, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b4bdbbd to 2ff239f Compare May 31, 2023 15:15
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.31.3 chore(deps): update dependency vitest to v0.31.4 Jun 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 2ff239f to ae5c59f Compare June 1, 2023 11:26
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.31.4 chore(deps): update dependency vitest to v0.32.0 Jun 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from ae5c59f to 3131254 Compare June 6, 2023 19:16
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.32.0 chore(deps): update dependency vitest to v0.32.1 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 3131254 to 103a02d Compare June 16, 2023 15:33
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.32.1 chore(deps): update dependency vitest to v0.32.2 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 103a02d to e0a0b98 Compare June 16, 2023 18:30
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.32.2 chore(deps): update dependency vitest to v0.32.3 Jul 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e0a0b98 to 34ca0db Compare July 3, 2023 10:18
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.32.3 chore(deps): update dependency vitest to v0.32.4 Jul 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 34ca0db to 848703d Compare July 3, 2023 14:17
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.32.4 chore(deps): update dependency vitest to v0.33.0 Jul 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 848703d to ab98d45 Compare July 6, 2023 17:24
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.33.0 chore(deps): update dependency vitest to v0.34.0 Aug 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from ab98d45 to d87b89f Compare August 1, 2023 16:29
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.0 chore(deps): update dependency vitest to v0.34.1 Aug 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d87b89f to 7b4a007 Compare August 1, 2023 18:38
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.1 chore(deps): update dependency vitest to v0.34.2 Aug 17, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 7b4a007 to ec6c5a0 Compare August 17, 2023 13:28
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.2 chore(deps): update dependency vitest to v0.34.3 Aug 25, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from ec6c5a0 to 918c676 Compare August 25, 2023 11:27
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.3 chore(deps): update dependency vitest to v0.34.3 - autoclosed Aug 29, 2023
@renovate renovate bot closed this Aug 29, 2023
@renovate renovate bot deleted the renovate/vitest-monorepo branch August 29, 2023 03:57
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.3 - autoclosed chore(deps): update dependency vitest to v0.34.3 Aug 29, 2023
@renovate renovate bot reopened this Aug 29, 2023
@renovate renovate bot restored the renovate/vitest-monorepo branch August 29, 2023 04:16
@renovate renovate bot changed the title chore(deps): update dependency vitest to v0.34.3 chore(deps): update dependency vitest to v0.34.3 - autoclosed Aug 29, 2023
@renovate renovate bot deleted the renovate/vitest-monorepo branch August 29, 2023 05:08
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.

1 participant