chore: upgrade vitest to 0.34.6

[yonadaaa]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: cbfe370

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[yonadaaa]

It seems toEqualTypeOf is bugged with zod: vitest-dev/vitest#4114

[yonadaaa]

I can't find a version that fixes the benchmarking issue but doesn't also introduce this MISMATCH issue... wonder if it's worth just upgrading vitest in store-sync where we really need it.

[holic]

just upgrading store-sync seems fine to me!

could also try bumping zod to see if this was fixed there?

[holic]

intentionally not bumping this one?

[yonadaaa]

woops, missed that in my ctrl-f

[holic]

just upgrading store-sync seems fine to me!

could also try bumping zod to see if this was fixed there?

[tash-2s]

The errors in the previous PR #2190 appear to be caused by the following reasons, though not confirmed:

1. Error: Definitions of the following identifiers conflict with those in another file
   • vitest v1 requires vite v5, but mud uses vite v4.
2. Error: Cannot find module 'rollup/parseAst' or its corresponding type declarations.
   • vite v5, installed via vitest v1, doesn't support moduleResolution: node10, which mud uses. This is because vite v5's rollup doesn't fully support node10.
   • mud's moduleResolution issue is tracked at Current TypeScript packages setup and improvement suggestion #2051.
3. Error: Cannot find name 'WeakKey'
   • Recent versions of vitest require typescript v5.2 or newer, but mud uses v5.1.

Regarding the toEqualTypeOf problem, it seems there is no easy fix at the moment. toMatchTypeOf is a looser alternative than toEqualTypeOf, as it allows extra properties, but it works.

[holic]