Skip to content
This repository was archived by the owner on Oct 23, 2023. It is now read-only.

chore(deps): update vitest monorepo#453

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/vitest-monorepo
Open

chore(deps): update vitest monorepo#453
renovate[bot] wants to merge 1 commit intomainfrom
renovate/vitest-monorepo

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Jun 6, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-c8 (source) 0.31.4 -> 0.33.0 age adoption passing confidence
vitest 0.31.4 -> 0.34.6 age adoption passing confidence

Release Notes

vitest-dev/vitest (@​vitest/coverage-c8)

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

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 12 times, most recently from b5c80f1 to 0dd7663 Compare June 13, 2023 14:18
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 5 times, most recently from 3a51d72 to db71352 Compare June 15, 2023 20:39
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.32.0 chore(deps): update vitest monorepo to v0.32.1 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from db71352 to 1c5d25d Compare June 16, 2023 14:46
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.32.1 chore(deps): update vitest monorepo to v0.32.2 Jun 16, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 10 times, most recently from be24834 to 1026f83 Compare June 22, 2023 22:39
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 6 times, most recently from 3ccf6d5 to 450bade Compare July 1, 2023 19:22
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.32.2 chore(deps): update vitest monorepo to v0.32.3 Jul 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 450bade to 511734e Compare July 3, 2023 09:36
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.32.3 chore(deps): update vitest monorepo to v0.32.4 Jul 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from 78da806 to 232e728 Compare July 6, 2023 11:01
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.32.4 chore(deps): update vitest monorepo to v0.33.0 Jul 6, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 11 times, most recently from 4717230 to 6fe4813 Compare July 13, 2023 06:07
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch 4 times, most recently from e7ea3a1 to e18a009 Compare July 15, 2023 07:23
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants