chore(deps-dev): bump vitest from 0.24.5 to 0.25.1

[dependabot]

Bumps vitest from 0.24.5 to 0.25.1.

Release notes

Sourced from vitest's releases.

v0.25.1

   🚀 Features

• Add vi.setConfig helper  -  by @​sheremet-va in vitest-dev/vitest#2293
• Allow hooks to be executed in a stack or list  -  by @​sheremet-va in vitest-dev/vitest#2294

   🐞 Bug Fixes

• Always rewrite defined jsdom keys  -  by @​sheremet-va in vitest-dev/vitest#2290
• Default reporter regression  -  by @​antfu in vitest-dev/vitest#2292
• Don't fail bench when using options  -  by @​poyoho in vitest-dev/vitest#2295

    View changes on GitHub

v0.25.0

   ✅ Builtin TypeChecking

In v0.25.0, Vitest allows you to write tests for your types, using expectTypeOf or assertType syntaxes. By default all tests inside *.test-d.ts files are considered type tests. Run vitest typecheck to run type tests.

// my.test-d.ts
import { assertType, expectTypeOf } from 'vitest'
import { mount } from './mount.js'
test('my types work properly', () => {
expectTypeOf(mount).toBeFunction()
expectTypeOf(mount).parameter(0).toMatchTypeOf<{ name: string }>()
// @​ts-expect-error name is a string
assertType(mount({ name: 42 }))
})

Learn more at the documentation and this RFC

   🚨 Breaking Changes

• Return context in startVitest()  -  by @​antfu in vitest-dev/vitest#2072

   🚀 Features

• onTestFailed hook  -  by @​antfu in vitest-dev/vitest#2210
• Display error frame if present (like Vite)  -  by @​haikyuu and @​sheremet-va in vitest-dev/vitest#2257
• Benchmark table report  -  by @​poyoho in vitest-dev/vitest#2179
• Add typechecking functionality  -  by @​sheremet-va and @​antfu in vitest-dev/vitest#2107

   🐞 Bug Fixes

• Clear full screen only in watch mode  -  by @​sheremet-va (c3d89)

... (truncated)

Commits

• e1de945 chore: release v0.25.1
• 1703f7c fix: don't fail bench when using options (#2295)
• c386bce feat: allow hooks to be executed in a stack or list (#2294)
• f0b048b fix: default reporter regression (#2292)
• 922e525 fix: always rewrite defined jsdom keys (#2290)
• b1961f0 feat: add vi.setConfig helper (#2293)
• 70e1447 chore: update license
• 94f2e66 chore: release v0.25.0
• 7c7f33d feat: add typechecking functionality (#2107)
• 941ba37 chore: upgrade deps (#2286)
• 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 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)

[Uzlopak]

@climba03003

The vitest detection seems to be OK, but forcing ESM loader handling the files, does not result in loading the plugin.

[climba03003]

Supporting all those framework seems to be a heavy task.
🤯🤯🤯

[Uzlopak]

The unit tests for vitest break, when using versions of vitest >= 0.24.4.

[sheremet-va]

@climba03003

The vitest detection seems to be OK, but forcing ESM loader handling the files, does not result in loading the plugin.

What exactly do you test? If you want to test that others importing this library can use it, you need to add your source files to deps.exclude, since this is how they will run for those who don't inline fastify-autoload.

This is probably a regression still, and I will look into it. But there is also a case, where this might be desirable behaviour, and you need to disable deps.interopDefault (Vitest should probably do it by itself, when environment is node).

[Uzlopak]

@sheremet-va

It seems that vitest-dev/vitest#2226 broke our code.

[sheremet-va]

Should be fixed in 0.25.2.

[Uzlopak]

Thank you very much

[Uzlopak]

@dependabot recreate

[dependabot]

Superseded by #279.