vite is fixed to version 3.0.2 in sveltejs/kit 1.0.0-next.418 ?

[kuchaguangjie]

Describe the bug

I get following error in github action:

 ERR_PNPM_PEER_DEP_ISSUES  Unmet peer dependencies

.
└─┬ @sveltejs/kit 1.0.0-next.418
  └── ✕ unmet peer vite@3.0.2: found 3.0.8

hint: If you don't want pnpm to fail on peer dependency issues, add "strict-peer-dependencies=false" to an .npmrc file at the root of your project.

In my package.json, it's "vite": "^3.0.7".
Is there a reason to make vite fix to 3.0.2 ?

Reproduction

In package.json, set "vite": "^3.0.7", then start, and will get the above error.

Logs

No response

System Info

System:
    OS: Linux 5.14 Linux Mint 20.1 (Ulyssa)
    CPU: (8) x64 Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz
    Memory: 8.22 GB / 15.55 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 16.13.1 - ~/.nvm/versions/node/v16.13.1/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.13.1/bin/yarn
    npm: 8.17.0 - ~/.nvm/versions/node/v16.13.1/bin/npm
  Browsers:
    Chrome: 104.0.5112.79
  npmPackages:
    @sveltejs/adapter-auto: next => 1.0.0-next.64 
    @sveltejs/kit: next => 1.0.0-next.408 
    svelte: ^3.49.0 => 3.49.0 
    vite: ^3.0.7 => 3.0.7 

### Severity

serious, but I can work around it

### Additional Information

_No response_

[Conduitry]

It looks like this happened as part of #5730, which I assume was not intended.

There are currently reasons for SvelteKit's copy of Vite for its own test suite to be pinned, but that shouldn't have been reflected in its peerDependency on Vite.