fix(playground): typecheck

[fi3ework]

Description

pass type check error introduced in #12207.
CI is failed on HEAD for now https://github.com/vitejs/vite/actions/runs/4366725444/jobs/7637110095.
But it's weird in #12207 all the tests are passed, are there some flaw in the CI flow 🤔

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the PR Title Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[fi3ework]

Not only type check, there's also 1 failed test case.

---

CI passed, why all CI failed in https://github.com/vitejs/vite/actions/runs/4366725444/jobs/7637110752 with following errors 😅

FAIL  playground/css/__tests__/no-css-minify/no-css-minify.spec.ts [ playground/css/__tests__/no-css-minify/no-css-minify.spec.ts ]
Error: [vite]: Rollup failed to resolve import "#alias" from "/home/runner/work/vite/vite/playground-temp/css/main.js".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
`build.rollupOptions.external`
 ❯ Object.onwarn node_modules/.pnpm/rollup@3.18.0/node_modules/rollup/dist/es/shared/node-entry.js:24[95](https://github.com/vitejs/vite/actions/runs/4366725444/jobs/7637110752#step:14:96)0:13
 ❯ ModuleLoader.handleInvalidResolvedId node_modules/.pnpm/rollup@3.18.0/node_modules/rollup/dist/es/shared/node-entry.js:23632:26
 ❯ node_modules/.pnpm/rollup@3.18.0/node_modules/rollup/dist/es/shared/node-entry.js:23592:26

[fi3ework]

cc @patak-dev @bluwy The error might block other PR's CI. Could merge this early.

[patak-dev]

Thanks for taking care of this @fi3ework!

[bluwy]

Thanks for fixing this! It sometimes happen because the old PR CI was ran against the old main branch.