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 #48

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 7, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@vitest/coverage-c8 (source) 0.23.4 -> 0.33.0 age adoption passing confidence
vitest (source) 0.23.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

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

v0.31.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.31.0

Compare Source

   🚨 Breaking Changes
  • Remove browser from allowed pools inside poolMatchGlob config option. Please, use Vitest workspaces for running tests in the browser.

  • Move assertion declarations to expect package  -  by @​sheremet-va in https://github.com/vitest-dev/vitest/issues/3294 (cf3af)

    • The change should be minor:
    - declare namespace Vi {
    + declare module 'vitest' {
       interface Assertion<T = any> extends CustomMatchers<T> {}
       interface AsymmetricMatchersContaining extends CustomMatchers {}
    }
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.30.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.30.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.29.8

Compare Source

   🚀 Features
  • Allow accessing "vi

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.

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

@vercel
Copy link

vercel bot commented Oct 7, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
artifact-viewer ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 29, 2023 3:48pm

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 22d193b to 790c19e Compare October 10, 2022 16:18
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.24.0 chore(deps): update vitest monorepo to v0.24.1 Oct 10, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 790c19e to 62b3af0 Compare October 14, 2022 12:53
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.24.1 chore(deps): update vitest monorepo to v0.24.3 Oct 14, 2022
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.24.3 chore(deps): update vitest monorepo to v0.24.4 Oct 31, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 62b3af0 to 832d886 Compare October 31, 2022 11:23
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 832d886 to b616e17 Compare November 1, 2022 20:09
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.24.4 chore(deps): update vitest monorepo to v0.24.5 Nov 1, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b616e17 to 3b94f1d Compare November 7, 2022 19:27
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.24.5 chore(deps): update vitest monorepo to v0.25.0 Nov 7, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 3b94f1d to fb8d410 Compare November 8, 2022 18:02
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.25.0 chore(deps): update vitest monorepo to v0.25.1 Nov 8, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from fb8d410 to 6c62585 Compare November 14, 2022 14:31
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.25.1 chore(deps): update vitest monorepo to v0.25.2 Nov 14, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 6c62585 to 660471e Compare November 22, 2022 14:56
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.25.2 chore(deps): update vitest monorepo to v0.25.3 Nov 22, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 660471e to 4b07c46 Compare December 5, 2022 20:19
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.25.3 chore(deps): update vitest monorepo to v0.25.4 Dec 5, 2022
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 4b07c46 to bc599da Compare December 6, 2022 19:07
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 7815e33 to 9d2a4c7 Compare June 16, 2023 13:50
@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 9d2a4c7 to 5e93bdf Compare June 16, 2023 17:34
@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 from 5e93bdf to 7e1e083 Compare July 3, 2023 08:44
@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 7e1e083 to 3e71009 Compare July 3, 2023 11:54
@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 from 3e71009 to 3d6b28e Compare July 6, 2023 17:57
@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 from 3d6b28e to 6b5da1f Compare August 1, 2023 20:37
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.33.0 chore(deps): update vitest monorepo Aug 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 6b5da1f to 936e8fa Compare August 17, 2023 12:21
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 936e8fa to 5c73c89 Compare August 25, 2023 09:28
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 5c73c89 to 9e17def Compare September 8, 2023 12:28
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 9e17def to 0d2b2c4 Compare September 21, 2023 15:42
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