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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 10, 2023

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 (source) 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

@codecov
Copy link

codecov bot commented Jun 10, 2023

Codecov Report

All modified lines are covered by tests ✅

Comparison is base (0ec1fa7) 100.00% compared to head (1a4948b) 100.00%.

❗ Current head 1a4948b differs from pull request most recent head 6897d69. Consider uploading reports for the commit 6897d69 to get more accurate results

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #114   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            6         6           
  Lines          135       135           
  Branches        26        26           
=========================================
  Hits           135       135           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@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 78bc970 to fa897be Compare June 16, 2023 13:30
@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 fa897be to 15c45b5 Compare June 16, 2023 16:16
@renovate renovate bot changed the title chore(deps): update vitest monorepo to v0.32.2 chore(deps): update vitest monorepo to v0.32.4 Jul 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 15c45b5 to 65c4978 Compare July 3, 2023 11:55
@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 65c4978 to 1a4948b Compare July 6, 2023 15:46
@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 2 times, most recently from 2aef258 to 13b52b9 Compare August 1, 2023 19:34
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 13b52b9 to fccb963 Compare August 17, 2023 11:14
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from fccb963 to e92377a Compare August 25, 2023 08:15
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e92377a to d67c583 Compare September 8, 2023 13:12
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d67c583 to a6b5ebd Compare September 21, 2023 16:53
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from a6b5ebd to 6897d69 Compare September 29, 2023 16:04
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