Upgrade packages vitest and @vitest/coverage-v8

[palisadoes]

Rationale

1. This was previously attempted by the automated dependabot job but the PR tests failed.
2. This issue has been created to fix the issue as there may be multiple dependency requirements that need updating

This is a major revision upgrade and many files may need to be updated to the new syntax, functions, methods and classes

Task

1. Upgrade vitest and @vitest/coverage-v8. These dependencies needed to be updated together.
2. Remove this package if it is:
   1. unused
   2. unnecessary. For example:
      1. the functionality can be maintained by using another package we are already using,
      2. If we are using only one function or class in the package you can consider replacing it with code that resides in this repository
      3. It is used by a feature that the end user is unlikely to ever use

Background Failing PRs

• chore(deps): bump vitest and @vitest/coverage-v8 #2400
• https://github.com/PalisadoesFoundation/talawa-api/actions/runs/9942874372/job/27465367373?pr=2400

Release Note Details

Bumps vitest and @vitest/coverage-v8. These dependencies needed to be updated together.
Updates vitest from 1.6.0 to 2.0.3

Release notes

Sourced from vitest's releases.

v2.0.3

   🚀 Features

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

   🐞 Bug Fixes

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

    View changes on GitHub

v2.0.2

   🐞 Bug Fixes

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

   🏎 Performance

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

    View changes on GitHub

v2.0.1

   🐞 Bug Fixes

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

    View changes on GitHub

v2.0.0

... (truncated)

Commits

• 81b8d67 chore: release v2.0.3
• 09dc75c chore(deps): update dependency @​edge-runtime/vm to v4 (#6047)
• f851982 fix: --inspect-brk stop on Windows (#6110)
• 99a12ae chore: release v2.0.2
• 80a43d5 fix(browser): inline pretty-format and replace picocolors with tinyrainbow (#...
• 7012f8c docs: add env documentation (#6063)
• 16eb6c8 chore: release v2.0.1
• 4b03e72 fix(browser): correctly inherit browser config in a workspace (#6054)
• 4d5597d fix(vitest): print only running files, not every file (#6052)
• 1b150a3 chore: release v2.0.0
• Additional commits viewable in compare view

Updates @vitest/coverage-v8 from 1.6.0 to 2.0.3

Release notes

Sourced from @​vitest/coverage-v8's releases.

v2.0.3

   🚀 Features

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

   🐞 Bug Fixes

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

    View changes on GitHub

v2.0.2

   🐞 Bug Fixes

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

   🏎 Performance

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

    View changes on GitHub

v2.0.1

   🐞 Bug Fixes

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

    View changes on GitHub

v2.0.0

... (truncated)

Commits

• 81b8d67 chore: release v2.0.3
• 99a12ae chore: release v2.0.2
• 80a43d5 fix(browser): inline pretty-format and replace picocolors with tinyrainbow (#...
• 16eb6c8 chore: release v2.0.1
• 1b150a3 chore: release v2.0.0
• 5611895 chore: release v2.0.0-beta.13
• 368c137 fix(coverage): remove work-around for implicit else (#6014)
• 05d5f38 chore(deps): update all non-major dependencies (#5957)
• 169bc1f fix(coverage): support overriding exclude (#5997)
• cd9cc6b chore: release v2.0.0-beta.12
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[akash0708]

Hello @palisadoes . I have been looking forward to contribute to Talawa for a long time, would have loved to work on this issue but, I cannot find the packages being used in the repo. Neither of them are present in the list of dependencies or devDependencies in package.json. Can anyone please help me out a bit?

[varshith257]

@akash0708 What dependencies you are looking at? If new packages needed in upgradation of vitest , go ahead with them

[akash0708]

@varshith257 as of now there is no existence of vitest anywhere in package.json , so what should I update? Should I install it?

[varshith257]

@akash0708 Sorry for the confusion! This is an issue in the talawa-api. I will move there. Would you like to work on this?

[akash0708]

@varshith257 yes I would like to work on this issue.

[akash0708]

Hello I've upgraded vitest and @vitest/coverage-v8 to the required versions, but am encountering this error when I try to commit. Any idea regarding how I should go about debugging it?

I have not changed any of these files. I have just updated the required dependencies.

[palisadoes]

Please ask the #talawa-api slack channel. Make sure you are making edits to a local branch based on the most current develop branch.

[akash0708]

Yes I am working on the latest develop branch. I have asked my query in the slack channel.

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[palisadoes]

unassigning. inactivity

[ARYANSHAH1567]

Can you assign the issue to me?

[palisadoes]

@ARYANSHAH1567

Our policy is to assign no more than two issues to each contributor across all repositories. This way everyone gets a chance to participate in the projects. We sometimes give exceptions for more urgent cases and sometimes we lose track, but the policy stands. You have reached your limit, please wait until your existing issues are closed before requesting more issues. You could unassign yourself from one of the other issues too.

[akshayw1]

Can I get the issue assigned @Cioppolo14

[github-actions]

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

[Cioppolo14]

@akshayw1 Are you working on this?

[akshayw1]

Yes, need 3 days more, Will raise a PR