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 vitest monorepo #37

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 3, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/browser (source) ^0.29.7 -> ^0.34.0 age adoption passing confidence
@vitest/coverage-c8 (source) ^0.29.7 -> ^0.33.0 age adoption passing confidence
@vitest/ui (source) ^0.29.7 -> ^0.34.0 age adoption passing confidence
vitest (source) ^0.29.7 -> ^0.34.0 age adoption passing confidence

Release Notes

vitest-dev/vitest (@​vitest/browser)

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
   🐞 Bug Fixes
    View changes on GitHub

v0.31.3

Compare Source

   🚀 Features
  • Support `V

Configuration

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

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • 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 force-pushed the renovate/vitest-monorepo branch 3 times, most recently from 0989e21 to 6222122 Compare May 10, 2023 00:33
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 5 times, most recently from 5afc281 to 5ab30e9 Compare May 19, 2023 18:50
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 5ab30e9 to 87f247a Compare May 22, 2023 09:47
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from b879729 to 1869327 Compare June 3, 2023 11:47
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 1869327 to 240a0f7 Compare June 5, 2023 14:53
@renovate renovate bot changed the title chore(deps): update vitest monorepo to ^0.31.0 chore(deps): update vitest monorepo to ^0.32.0 Jun 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 3 times, most recently from a575dc3 to 028e01b Compare June 12, 2023 13:45
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 2 times, most recently from d02f409 to 10d204a Compare June 21, 2023 15:55
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 5 times, most recently from 1bee5ad to 5bdd3e2 Compare June 27, 2023 13:18
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 694e811 to 7c623f4 Compare July 6, 2023 18:15
@renovate renovate bot changed the title chore(deps): update vitest monorepo to ^0.32.0 chore(deps): update vitest monorepo to ^0.33.0 Jul 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 0150739 to bd43634 Compare February 19, 2024 04:53
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 7 times, most recently from cee66cd to ca7526f Compare February 26, 2024 00:22
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 17 times, most recently from c762f92 to abbd6c5 Compare May 25, 2024 18:07
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from abbd6c5 to 033bb08 Compare May 25, 2024 21: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.

None yet

0 participants