[Snyk] Upgrade vitest from 0.33.0 to 2.0.5

[WontonSam]

Snyk has created this PR to upgrade vitest from 0.33.0 to 2.0.5.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

• The recommended version is 52 versions ahead of your current version.

• The recommended version was released on 22 days ago.

Release notes

Package name: vitest

• 2.0.5 - 2024-07-31
  

     🚀 Features

  • Introduce experimental reported tasks  -  by @ sheremet-va in #6149 (13d85)
    • This is part of the experimental API and doesn't follow semver. We are hoping to stabilize it for 2.1. If you are working with custom reporters, give this a go!

     🐞 Bug Fixes

  • Show a difference between string characters if both values are strings  -  by @ sheremet-va in #6191 (29176)
  • testNamePattern adds leading space  -  by @ AriPerkkio in #6186 (073a5)
  • browser:
    • Don't bundle afterEach cleanup hooks in node entrypoint  -  by @ sheremet-va in #6192 (e6fbc)
    • UserEvent.setup initiates a separate state for userEvent instance  -  by @ sheremet-va in #6088 (883f3)
    • Correctly import optimized module in vi.importActual  -  by @ sheremet-va in #6219 (804ff)
    • Passing options to hover/unhover  -  by @ MNeverOff in #6175 (d4c00)
    • Improve unique CSS selector generation  -  by @ zacharyvoase and Zack Voase in #6243 (e7acd)
  • vitest:
    • Remove nuxt from auto inline deps  -  by @ sheremet-va (93882)
    • Improve defineProject and defineWorkspace types  -  by @ sheremet-va in #6198 (8cd82)
    • Correctly resolve mocked node:* imports in __mocks__ folder  -  by @ sheremet-va in #6204 (a48be)
  • web-worker:
    • Expose globals on self  -  by @ sheremet-va in #6170 (12bb5)

      View changes on GitHub

• 2.0.4 - 2024-07-22
  

     🐞 Bug Fixes

  • One-line environment options  -  by @ hahanein in #5105 (38269)
  • Resolve assets imported with require  -  by @ sheremet-va in #6159 (807a2)
  • browser:
    • Don't panic if @ vitest/browser is installed outside of project root  -  by @ sheremet-va in #6135 (ccfcd)
    • Set global filepath  -  by @ sheremet-va in #6190 (0d0b4)
    • Allow preview and open in the editor screenshot error from ui  -  by @ userquin in #6113 (2d620)
  • coverage:
    • Global thresholds to include files from glob thresholds  -  by @ thor-juhasz and @ AriPerkkio in #6172 (02e3f)
    • Consistent type-only file handling  -  by @ AriPerkkio in #6183 (90576)
    • Ignore *.cts files  -  by @ AriPerkkio in #6189 (5da45)
    • Add thresholds.<glob>.100 option  -  by @ thor-juhasz and @ AriPerkkio in #6174 (f6845)
  • spy:
    • Fix mockImplementation for function overload and unions  -  by @ hi-ogawa in #6181 (7a75b)

      View changes on GitHub

• 2.0.3 - 2024-07-15
  

     🚀 Features

  • ui: Show all suites/tests when parent matches  -  by @ userquin in #6106 (840e0)

     🐞 Bug Fixes

  • --inspect-brk stop on Windows  -  by @ AriPerkkio in #6110 (f8519)
  • browser:
    • Don't import from "vite"  -  by @ sheremet-va (35655)
    • Allow immidiate reinvalidation of mocked dependencies  -  by @ sheremet-va in #6108 (f44cc)
  • spy:
    • Fix type error when assigning vi.spyOn to MockInstance of function overload  -  by @ hi-ogawa in #6086 (e9f9a)
  • vite-node:
    • Remove suffix slash on file protocol for window  -  by @ syi0808 in #6109 (93ebd)

      View changes on GitHub

• 2.0.2 - 2024-07-10
  

     🐞 Bug Fixes

  • browser:
    • Remove @ vitest/runner > pretty-format from prebundling because it doesn't exist  -  by @ sheremet-va in #6075 (a169d)
    • Inline pretty-format and replace picocolors with tinyrainbow  -  by @ sheremet-va in #6077 (80a43)
    • Remove crypto.randomUUID from the client  -  by @ userquin in #6079 (04c83)
    • Correctly overwrite loupe require  -  by @ sheremet-va (756ac)
    • Dedupe @ vitest/browser/client  -  by @ sheremet-va in #6081 (ee725)
    • Don't release keyboard automatically  -  by @ sheremet-va in #6083 (58fac)
  • ui:
    • Test files notified only when running  -  by @ userquin in #6069 (af7fe)
    • Encode html entities in task name  -  by @ userquin and @ sheremet-va in #6070 (7f0cc)
  • web-worker:
    • Peer dependency version on vitest  -  by @ AriPerkkio in #6060 (95a2d)

     🏎 Performance

  • browser: Don't import msw if no modules are mocked  -  by @ sheremet-va in #6073 (aa527)

      View changes on GitHub

• 2.0.1 - 2024-07-08
  

     🐞 Bug Fixes

  • browser: Correctly inherit browser config in a workspace  -  by @ sheremet-va in #6054 (4b03e)
  • ui: Move virtual scroller to dev dependencies  -  by @ userquin in #6053 (f94ed)
  • vitest: Print only running files, not every file  -  by @ sheremet-va in #6052 (4d559)

      View changes on GitHub

• 2.0.0 - 2024-07-08
  

  Vitest 2.0 is here! This release page lists all changes made to the project during the beta. For the migration guide, please refer to the documentation.

  🚨 Breaking Changes

  • Simplify mock function generic types and align with jest - by @ hi-ogawa in #4784 (a0c1d37)
  • Remove --segfault-retry - by @ sheremet-va in #5514 (ed60e)
    • This flag was introduced to combat threads segfaults. Our current recommendation is to use the new default forks pool instead.
  • Run suite hooks in a stack - by @ sheremet-va in #5609 (1277d)
    • This feels like a more sensible default. Especially with the new onTestFinished hook. This can make your tests run a little bit slower.
  • Enable coverage.ignoreEmptyLines by default - by @ AriPerkkio in #5543 (31994)
    • ⚠️ This change may cause significant differences in your coverage results compared to Vitest v1. These changes are expected as coverage reporting is now more accurate. See #5423 for more details.
  • Add correct location and snapshot fields in json reporter - by @ sheremet-va in #5434 (bcccc)
    • Previously, the location field pointed to the error location instead of the test location. Now it is aligned with jest and contains the line and column of a test function, but requires includeTaskLocation to be enabled.
  • Update dependency chai to v5 - by renovate[bot] and @ sheremet-va in #5135 (73646)
  • Remove watchExclude - by @ patak-dev in #5177 (d7371)
  • Change default pool to 'forks' - by @ AriPerkkio in #5047 (7f8f9)
    • This change is done for compatibility issues
    • This pool may be slightly slower than previous threads pool: https://vitest.dev/guide/improving-performance.html#pool
  • --merge-reports to support coverage - by @ AriPerkkio in #5736 (b7438)
  • Add promise-based return assertions, do not auto-resolve returned promises - by @ sheremet-va in #5749 (5f710)
    • ⚠️ Vitest no longer unwraps promises in spy.mock.returns. If the function is async or returns a promise, it will always succeed and have a Promise in results. To make migration easier, we introduced spy.mock.settledResults that unwraps promises and expect().toHaveResolved() matcher that accepts unwrapped value.
  • Do not exit process if global setup has failed - by @ sheremet-va in #5726 (ddb09)
  • Don't exit process if config failed - by @ sheremet-va in #5715 (f232f)
  • Add meta to json output - by @ sheremet-va in #5802 (dd754)
  • Rename indexScripts to orchestratorScripts in the browser config - by @ sheremet-va in #5842 (49f34)
  • Add "vitest list" API to print collected tests without running them - by @ sheremet-va in #6013 (583dd)
    • ⚠️ This changes the custom pool API - now requires collectTests method alongside runTests.
  • Remove the empty suite from the runner - by @ sheremet-va in #5435 (dbbbe)
  • Support concurrent suites - by @ hi-ogawa in #5491 (222ce44)
  • Support overriding exclude in coverage - by @ AriPerkkio in #5997 (169bc)
    • ⚠️ Vitest coverage no longer adds test files to exclude patterns if coverage.exclude was overridden in the config. Add your test patterns manually, or merge your overrides with default ones: ['**/my-pattern.js', ...coverageConfigDefaults.exclude]. See https://vitest.dev/config/#coverage-exclude for an example.

  🚀 Features

  
  • browser:
    • 🌐 This release lays the groundwork for the next iteration of Vitest Browser Mode. You can read more about our future plans at Vitest Browser Mode vitest-dev/vitest#5828
    • Add commands to communicate betweens server and the browser - by @ sheremet-va in #5097 (aa431)
    • Do not reload the page during watch mode - by @ sheremet-va in #5810 (e5b9a)
    • Support changing the viewport - by @ sheremet-va in #5811 (71851)
    • Add browser iframe mouse interaction - by @ userquin in #5815 (f29b9)
    • Support click event - by @ sheremet-va in #5777 (839c3)
    • Rename none provider to preview, make it default - by @ sheremet-va in #5826 (18310)
    • Run tests in parallel in headless mode, add page.screenshot method - by @ sheremet-va in #5853 (81c42)
    • Implement several userEvent methods, add fill and dragAndDrop events - by @ sheremet-va in #5882 (4dbea)
    • Introduce expect.dom method and bundle jest-dom matchers with @ vitest/browser - by @ sheremet-va in #5910 (3a96a)
    • Expose CDP in the browser - by @ sheremet-va in #5938 (bec43)
    • Add "init" command for browser tests - by @ sheremet-va in #5960 (49e97)
    • Add an option to take screenshots if the browser test fails - by @ sheremet-va in #5975 (154cb)
    • Add tripleClick to interactive api - by @ userquin in #5987 (200a4)
    • Playwright provider doesn't allow resizing the browser viewport - by @ userquin and @ sheremet-va in #5984 (ff978)
  • Pretty print diffs coming from cause - by @ dubzzz in #5660 (6faf8)
  • Allow import statement as vi.mock path for better IDE support - by @ sheremet-va in #5690 (a99a1)
  • Remove deprecated options - by

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.