chore(deps): bump @types/chai to 5.0.1

[nopeless]

Description

#7121 cc @hi-ogawa

fix broken vitest assert types

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. If the feature is substantial or introduces breaking changes without a discussion, PR might be closed.
• Ideally, include a test that fails without this PR but passes with it.
• Please, don't make changes to pnpm-lock.yaml unless you introduce a new test example.

Tests

• Run the tests with pnpm test:ci. (vitest/test/config/fixtures/exec-args-fixtures/vmThreads.test.ts fails for some reason)

Documentation

• If you introduce new functionality, document it. You can run documentation with pnpm run docs command.

Changesets

• Changes in changelog are generated from PR name. Please, make sure that it explains your changes in an understandable manner. Please, prefix changeset messages with feat:, fix:, perf:, docs:, or chore:.

[nopeless]

note: I haven't actually checked if the typings work now, but based on a simple diff between v4 and v5, I concluded that bumping the version will fix the issue

[nopeless]

welp ci is breaking, idk y

[nopeless]

I am not entirely sure why 2130edc is required for build to succeed. I am also not sure why simply building the repository causes cced3ff either

[netlify]

✅ Deploy Preview for vitest-dev ready!

Built without sensitive environment variables

Name	Link
🔨 Latest commit	27904e3
🔍 Latest deploy log	https://app.netlify.com/sites/vitest-dev/deploys/676cbc2467bffc0008af9212
😎 Deploy Preview	https://deploy-preview-7123--vitest-dev.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[nopeless]

ci based tdd

[nopeless]

found out the type issue

Caused by this commit 5f4774f

I am not sure why he is inlining chai types when he already patched it? anyway, this is out of my decision.

This was not an issue in the previous @types/chai

4.3.6

declare namespace Chai {

5.0.1

declare global {
    namespace Chai {

@sheremet-va I would like to know how you would approach this issue

also I am not willing to fix the failing test as I have no idea why it fails

[hi-ogawa]

Hey, thanks for bringing the PR 👋
I suggested it without knowing much, but it looks fairly messy. Don't worry about this and we can take over this.

The idea of not having @types/chai in dependencies removes certain frictions in ts setup, so I get the idea. I'll push a few changes to test something.

---

Though patch is getting uglier, the basic typing should be working like before https://stackblitz.com/edit/vitest-dev-vitest-xrmchgds?file=test%2Fbasic.test.ts

[pkg-pr-new]

@vitest/browser

npm i https://pkg.pr.new/@vitest/browser@7123

@vitest/coverage-istanbul

npm i https://pkg.pr.new/@vitest/coverage-istanbul@7123

@vitest/expect

npm i https://pkg.pr.new/@vitest/expect@7123

@vitest/coverage-v8

npm i https://pkg.pr.new/@vitest/coverage-v8@7123

@vitest/mocker

npm i https://pkg.pr.new/@vitest/mocker@7123

@vitest/pretty-format

npm i https://pkg.pr.new/@vitest/pretty-format@7123

@vitest/runner

npm i https://pkg.pr.new/@vitest/runner@7123

@vitest/snapshot

npm i https://pkg.pr.new/@vitest/snapshot@7123

@vitest/spy

npm i https://pkg.pr.new/@vitest/spy@7123

@vitest/ui

npm i https://pkg.pr.new/@vitest/ui@7123

@vitest/utils

npm i https://pkg.pr.new/@vitest/utils@7123

vite-node

npm i https://pkg.pr.new/vite-node@7123

vitest

npm i https://pkg.pr.new/vitest@7123

@vitest/web-worker

npm i https://pkg.pr.new/@vitest/web-worker@7123

@vitest/ws-client

npm i https://pkg.pr.new/@vitest/ws-client@7123

commit: 27904e3