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 ^0.34.0 #8

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

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 21, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest (source) ^0.7.0 -> ^0.34.0 age adoption passing confidence
vitest (source) ^0.13.1 -> ^0.34.0 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

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

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 these updates again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@cr-gpt
Copy link

cr-gpt bot commented Mar 21, 2023

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables for this repo. you could follow readme for more information

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d78d645 to 5e0ac9b Compare March 21, 2023 13:39
@cr-gpt
Copy link

cr-gpt bot commented Mar 21, 2023

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables for this repo. you could follow readme for more information

@netlify
Copy link

netlify bot commented Mar 21, 2023

Deploy Preview for ant-design-webcomponents failed.

Name Link
🔨 Latest commit 765106f
🔍 Latest deploy log https://app.netlify.com/sites/ant-design-webcomponents/deploys/64c9e60451a7c00008632cec

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 5e0ac9b to a8bff0a Compare March 22, 2023 03:24
@cr-gpt
Copy link

cr-gpt bot commented Mar 22, 2023

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables for this repo. you could follow readme for more information

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from a8bff0a to 0dac272 Compare April 8, 2023 03:58
@cr-gpt
Copy link

cr-gpt bot commented Apr 8, 2023

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables for this repo. you could follow readme for more information

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 0dac272 to e33cc2d Compare April 9, 2023 14:41
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.29.0 chore(deps): update dependency vitest to ^0.30.0 Apr 9, 2023
@cr-gpt
Copy link

cr-gpt bot commented Apr 9, 2023

Seems you are using me but didn't get OPENAI_API_KEY seted in Variables for this repo. you could follow readme for more information

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e33cc2d to 4b8f582 Compare May 3, 2023 21:53
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.30.0 chore(deps): update dependency vitest to ^0.31.0 May 3, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 4b8f582 to 9de1df8 Compare June 9, 2023 23:52
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.31.0 chore(deps): update dependency vitest to ^0.32.0 Jun 9, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 9de1df8 to dcae403 Compare July 7, 2023 23:59
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.32.0 chore(deps): update dependency vitest to ^0.33.0 Jul 7, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from dcae403 to 765106f Compare August 2, 2023 05:13
@renovate renovate bot changed the title chore(deps): update dependency vitest to ^0.33.0 chore(deps): update dependency vitest to ^0.34.0 Aug 2, 2023
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