Bump vitest from 4.0.18 to 4.1.1

[dependabot]

Bumps vitest from 4.0.18 to 4.1.1.

Release notes

Sourced from vitest's releases.

v4.1.1

   🚀 Features

• experimental:
  • Expose matchesTags to test if the current filter matches tags  -  by @​sheremet-va in vitest-dev/vitest#9913 (eec53)
  • Introduce experimental.vcsProvider  -  by @​sheremet-va in vitest-dev/vitest#9928 (56115)

   🐞 Bug Fixes

• Mark TestProject.testFilesList internal properly  -  by @​sapphi-red in vitest-dev/vitest#9867 (54f26)
• Detect fixture that returns without calling use  -  by @​oilater in vitest-dev/vitest#9831 and vitest-dev/vitest#9861 (633ae)
• Drop vite 8.beta support  -  by @​AriPerkkio in vitest-dev/vitest#9862 (b78f5)
• Type regression in vi.mocked() static class methods  -  by @​purepear and @​hi-ogawa in vitest-dev/vitest#9857 (90926)
• Properly re-evaluate actual modules of mocked external  -  by @​hi-ogawa in vitest-dev/vitest#9898 (ae5ec)
• Preserve coverage report when html reporter overlaps  -  by @​hi-ogawa in vitest-dev/vitest#9889 (2d81a)
• Provide vi.advanceTimers to the preview provider  -  by @​sheremet-va in vitest-dev/vitest#9891 (1bc3e)
• Don't leak event listener in playwright provider  -  by @​sheremet-va in vitest-dev/vitest#9910 (d9355)
• Open browser in --standalone mode without running tests  -  by @​sheremet-va in vitest-dev/vitest#9911 (e78ad)
• Guard disposable and optional body  -  by @​sheremet-va in vitest-dev/vitest#9912 (6fdb2)
• Resolve retry.condition RegExp serialization issue  -  by @​nstepien and @​hi-ogawa in vitest-dev/vitest#9942 (7b605)
• collect:
  • Don't treat extra props on test return as tests  -  by @​sheremet-va in vitest-dev/vitest#9871 (141e7)
• coverage:
  • Simplify provider types  -  by @​AriPerkkio in vitest-dev/vitest#9931 (aaf9f)
  • Load built-in provider without module runner  -  by @​AriPerkkio in vitest-dev/vitest#9939 (bf892)
• expect:
  • Soft assertions continue after .resolves/.rejects promise errors  -  by @​mixelburg, Maks Pikov, Claude Opus 4.6 (1M context) and @​hi-ogawa in vitest-dev/vitest#9843 (6d74b)
  • Fix sinon-chai style API  -  by @​hi-ogawa in vitest-dev/vitest#9943 (0f08d)
• pretty-format:
  • Limit output for large object  -  by @​hi-ogawa and Claude Opus 4.6 (1M context) in vitest-dev/vitest#9949 (0d5f9)

    View changes on GitHub

v4.1.0

Vitest 4.1 is out!

This release page lists all changes made to the project during the 4.1 beta. To get a review of all the new features, read our blog post.

   🚀 Features

• Return a disposable from doMock()  -  by @​kirkwaiblinger in vitest-dev/vitest#9332 (e3e65)
• Added chai style assertions  -  by @​ronnakamoto and @​sheremet-va in vitest-dev/vitest#8842 (841df)
• Update to sinon/fake-timers v15 and add setTickMode to timer controls  -  by @​atscott and @​sheremet-va in vitest-dev/vitest#8726 (4b480)
• Expose matcher types  -  by @​sheremet-va in vitest-dev/vitest#9448 (3e4b9)
• Add toTestSpecification to reported tasks  -  by @​sheremet-va in vitest-dev/vitest#9464 (1a470)
• Show a warning if vi.mock or vi.hoisted are declared outside of top level of the module  -  by @​sheremet-va in vitest-dev/vitest#9387 (5db54)
• Track and display expectedly failed tests (.fails) in UI and CLI  -  by @​Copilot, sheremet-va and @​sheremet-va in vitest-dev/vitest#9476 (77d75)
• Support tags  -  by @​sheremet-va in vitest-dev/vitest#9478 (de7c8)
• Implement aroundEach and aroundAll hooks  -  by @​sheremet-va in vitest-dev/vitest#9450 (2a8cb)
• Stabilize experimental features  -  by @​sheremet-va in vitest-dev/vitest#9529 (b5fd2)

... (truncated)

Commits

• 1f2d318 chore: release v4.1.1
• ebfde79 refactor: rename matchesTagsFilter to matchesTags (#9956)
• 5611500 feat(experimental): introduce experimental.vcsProvider (#9928)
• eec53d9 feat(experimental): expose matchesTagsFilter to test if the current filter ...
• bf89208 fix(coverage): load built-in provider without module runner (#9939)
• 5a60868 refactor: fix typos (#9950)
• aaf9f18 fix(coverage): simplify provider types (#9931)
• 6fdb2ba fix: guard disposable and optional body (#9912)
• e78adcf fix: open browser in --standalone mode without running tests (#9911)
• ae5ec03 fix: properly re-evaluate actual modules of mocked external (#9898)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

QA Instructions

QA Testing Instructions for PR: Bump vitest from 4.0.18 to 4.1.1

---

Summary

This PR upgrades the vitest dependency from version 4.0.18 to 4.1.1. The new version includes multiple feature enhancements, bug fixes, and breaking changes, such as the deprecation of vite 8.beta support, updated APIs, and fixes for existing functionality. The aim of this PR is to take advantage of the improvements in the latest version to maintain compatibility and ensure optimized testing workflows.

---

Test Environment Setup

1. Pull this branch and run npm install or yarn to ensure the updated dependency (vitest@4.1.1) and its additional dependencies are installed.
2. Make sure the test suite runs in a development environment. This includes:
   • Node.js version compatible with the application.
   • Any custom vitest configurations in the vite.config.ts, vitest.config.ts, or equivalent files.
   • Access to any mocked modules or environment variables used in testing.

---

Test Scenarios

1. Run Existing Tests

• Steps:
  1. Execute the test suite using vitest (e.g., npm run test or yarn test).
• Expected Results:
  • All tests should pass as before.
  • There should be no unexpected errors or deprecations in the test output.
  • Verify that coverage reports are properly generated in HTML format.

2. Test for new vitest@4.1.1 changes

• Steps:
  • Create a custom test using the new doMock() feature to validate its behavior.

    import { doMock } from 'vitest';
    test('example test', () => {
      const disposable = doMock('./module-to-mock');
      expect(disposable.dispose).toBeInstanceOf(Function);
    });
    

• Expected Results:
  • doMock() should return a disposable object that can dispose of the mock properly.

3. Validate Tags Matching (Experimental)

• Steps:
  1. Create new tests in your test directory and tag them with custom tags using the .tags property, e.g.,

     test('tagged test', { tags: ['myTag'] }, () => {
       expect(true).toBe(true);
     });

  2. Use vitest --tag myTag to filter on the custom myTag.
  3. Use vitest --tag nonExistentTag to filter an invalid tag.
• Expected Results:
  • Tests tagged with myTag should run successfully.
  • Tests with nonExistentTag should not execute.

4. Backward Compatibility with Existing Mocks & Timers

• Steps:
  1. Ensure existing tests that rely on vi.mock() or timer controls still work as expected.
  2. Validate new vi.advanceTimers is accessible and behaves as documented.
• Expected Results:
  • Mocking behavior remains consistent.
  • Timer-related tests (e.g., vi.advanceTimers) accurately handle timer manipulation.

---

Regression Risks

1. Deprecated vite 8.beta support: Ensure compatibility with the current vite version used in the project.
2. Changes to vi.mocked() or its helpers: Validate against any tests/mock usage within the codebase to ensure APIs haven’t broken.
3. Coverage generation: Verify that test coverage metrics are preserved and that coverage reports continue to function properly.

---

Things to Watch For

1. The experimental.vcsProvider and some tagging-related functionality are labeled as experimental. Confirm that enabling these features does not introduce unexpected non-backward-compatible changes.
2. Edge cases involving rejected/soft promises in vi.expect now use improved behavior. Review tests that validate promises with .resolves or .rejects for breaking changes.
3. Runtime dependency updates in the package-lock.json (e.g., @emnapi/core) should not affect runtime behavior outside vitest. Check if other application components are affected.

---

Perform these tests and confirm vitest and the overall project behave as expected post-upgrade. Update or fix any broken tests before merging this PR.

---

Generated by QA Instructions Action