Vitest mock feature not working correctly due to change introduced in vite v3.0.6

[luckylooke]

Describe the bug

So it seems that v3.0.6 introduced some breaking change unintentionally (semver). Vite v3.0.5 works as expected, also tested v3.1.8 table and v3.2.0-beta.2 as well, results both: NOK.

In following reproduction:
In v3.0.5 and lower the package vue-meta is mocked correctly.
In v3.0.6 and higher the package vue-meta is NOT mocked at all.

Reproduction

https://stackblitz.com/edit/vue-vitest-demo-gk83pk?file=package.json

Steps to reproduce

check console.. you will see failed test
once you change (downgrade) version of vite to v3.0.5 you will get passed test

Or you may navigate to working example here https://stackblitz.com/edit/vue-vitest-demo-nl2dub?file=package.json which already have set vite version 3.0.5

System Info

Stackblitz

System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 16.14.2 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 7.17.0 - /usr/local/bin/npm
  npmPackages:
    @vitejs/plugin-vue: ^3.0.1 => 3.1.2 
    vite: v3.0.6 => 3.0.6

Used Package Manager

npm

Logs

$ vitest --debug
Error: Unknown option --debug
at async ESMLoader.import (https://vue-vitest-demo-dz15mu.w.staticblitz.com/blitz.3c06ff333fff62d153837b0d0df85b8ed07b008f.js:6:1209286)
at async i.loadESM (https://vue-vitest-demo-dz15mu.w.staticblitz.com/blitz.3c06ff333fff62d153837b0d0df85b8ed07b008f.js:6:246623)
at async handleMainPromise (https://vue-vitest-demo-dz15mu.w.staticblitz.com/blitz.3c06ff333fff62d153837b0d0df85b8ed07b008f.js:6:989295) {
name: 'CACError'
}

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sapphi-red]

This is happening because of #8659 and vitest needs to use the new option introduced by #10071.
The downstream issue is this one: vitest-dev/vitest#1484