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

Merged
merged 3 commits into from
Aug 6, 2023

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jul 22, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
vitest ^0.12.6 -> ^0.34.0 age adoption passing confidence

Release Notes

vitest-dev/vitest (vitest)

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
   🐞 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

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Asia/Tokyo, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • 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 added the renovate label Jul 22, 2023
@vercel
Copy link

vercel bot commented Jul 22, 2023

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

Name Status Preview Comments Updated (UTC)
github-repo-search ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 6, 2023 6:54am

@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 4f1ee18 to 40de508 Compare July 22, 2023 04:02
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 40de508 to 31c2e93 Compare July 22, 2023 06:23
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 31c2e93 to a37d811 Compare July 22, 2023 09:29
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from a37d811 to 931236d Compare July 22, 2023 12:41
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 931236d to 73a3bf0 Compare July 23, 2023 07:07
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 73a3bf0 to 8a87598 Compare July 23, 2023 07:30
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 8a87598 to e277322 Compare July 23, 2023 12:01
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from e277322 to d0db147 Compare August 1, 2023 16:10
@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 1, 2023
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from d0db147 to b09d3a2 Compare August 6, 2023 05:30
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from b09d3a2 to 0db0e90 Compare August 6, 2023 05:33
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 0db0e90 to 7738d4d Compare August 6, 2023 05:35
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 7738d4d to 1f9c7b5 Compare August 6, 2023 05:39
@renovate renovate bot force-pushed the renovate/vitest-monorepo branch from 1f9c7b5 to 4c1d193 Compare August 6, 2023 05:45
@renovate
Copy link
Contributor Author

renovate bot commented Aug 6, 2023

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

Warning: custom changes will be lost.

@hakshu25 hakshu25 merged commit 78085d6 into main Aug 6, 2023
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant