fix(hmr): reload when components switch between vapor and vdom

[edison1105]

Description

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.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@vitejs/plugin-vue@714

npm i https://pkg.pr.new/@vitejs/plugin-vue-jsx@714

commit: c9e8df8

[Copilot]

Pull request overview

This pull request fixes an HMR (Hot Module Replacement) issue by ensuring that Vue components fully reload when switching between vapor and vdom compilation modes, rather than attempting a hot update which could cause inconsistencies.

• Adds a vapor mode check to hasScriptChanged function to detect mode transitions
• Uses @ts-expect-error directive consistent with the codebase pattern for forward compatibility with Vue 3.6
• Ensures components trigger a full reload when the vapor property changes between updates

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The new vapor mode detection logic lacks test coverage. While the playground has HMR tests for various scenarios, there are no tests verifying that the component reloads correctly when switching between vapor and vdom modes. Consider adding a test case that validates this behavior by toggling a component between vapor and non-vapor modes and verifying that HMR triggers a full reload rather than just a hot update.