Vite setup vue/ts object with packages name changed.

[1216892614]

Describe the bug

When I run npm i after setup, npm tell me several packages have renamed.

1. npm init vite@latest
2. Select a framework: vue -> vue-ts
3. cd to workspace
4. npm i
   after these simple steps, I get these npm warnings:

npm WARN deprecated vscode-pug-languageservice@0.29.8: WARNING: This project has been renamed to @volar/pug-language-service. Install using @volar/pug-language-service instead.
npm WARN deprecated vscode-vue-languageservice@0.29.8: WARNING: This project has been renamed to @volar/vue-language-service. Install using @volar/vue-language-service instead.
npm WARN deprecated vscode-typescript-languageservice@0.29.8: WARNING: This project has been renamed to @volar/typescript-language-service. Install using @volar/typescript-language-service instead.

Reproduction

I can not offer you a reproduction with web IDE, however it's realy easy to repeat in your pc terminal.

System Info

- System: wsl2 on windows11
- editor: VSCode + Volar
It happend without browsers runing, so no need to offer browsers info.

Used Package Manager

npm

Logs

❯ npm i
npm WARN deprecated vscode-pug-languageservice@0.29.8: WARNING: This project has been renamed to @volar/pug-language-service. Install using @volar/pug-language-service instead.
npm WARN deprecated vscode-vue-languageservice@0.29.8: WARNING: This project has been renamed to @volar/vue-language-service. Install using @volar/vue-language-service instead.
npm WARN deprecated vscode-typescript-languageservice@0.29.8: WARNING: This project has been renamed to @volar/typescript-language-service. Install using @volar/typescript-language-service instead.

added 110 packages, and audited 111 packages in 2m

16 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

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 https://github.com/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.

[hydrati]

I probably know where the problem is. I may submit a PR for it later.