Upgrade vitest

[shauns]

WHY are these changes introduced?

Fixes https://github.com/Shopify/develop-app-inner-loop/issues/1826

WHAT is this pull request doing?

Upgrades vitest & vite across the board; fixes some test incompatibilities

How to test your changes?

• Run p test and p vitest
• Restart VS code and see that the vitest explorer is now working, and that tests can also be run directly from the editor

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
• Existing analytics will cater for this addition
• PR includes analytics changes to measure impact

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

[github-actions]

We detected some changes at either packages/*/src or packages/cli-kit/assets/cli-ruby/** and there are no updates in the .changeset.
If the changes are user-facing, run "pnpm changeset add" to track your changes and include them in the next release CHANGELOG.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	72.46% (+0.35% 🔼)	7392/10201
🟡	Branches	69.11%	3635/5260
🟡	Functions	71.58%	1962/2741
🟡	Lines	72.8% (-0.58% 🔻)	6978/9585

Test suite run success

1704 tests passing in 794 suites.

Report generated by 🧪jest coverage report action from 4de33b7

[github-actions]

Differences in type declarations

We detected differences in the type declarations generated by Typescript for this branch compared to the baseline ('main' branch). Please, review them to ensure they are backward-compatible. Here are some important things to keep in mind:

• Some seemingly private modules might be re-exported through public modules.
• If the branch is behind main you might see odd diffs, rebase main into this branch.

New type declarations

We found no new type declarations in this PR

Existing type declarations

packages/cli-kit/dist/public/node/fs.d.ts

@@ -1,6 +1,5 @@
 /// <reference types="node" resolution-mode="require"/>
 /// <reference types="node" resolution-mode="require"/>
-/// <reference types="node" resolution-mode="require"/>
 import { RandomNameFamily } from '../common/string.js';
 import { OverloadParameters } from '../../private/common/ts/overloaded-parameters.js';
 import { findUp as internalFindUp } from 'find-up';

[gonzaloriestra]

Nice work!

[gonzaloriestra]

Could you check if we can remove this? A punycode warning was shown with Node 22, and I think vite was one of the culprits.

[shauns]

I don't think it can be removed. The extensions console uses vite to build for instance

[gonzaloriestra]

I meant whatwg-url. Maybe with the Vite upgrade we don't need to pin this version anymore.