fix!: remove Vue 2 support

[mrhammadasif]

This pull request removes support for Vue 2 from the project. It updates documentation, peer dependencies, and example projects to reflect this change, and deletes all files related to Vue 2 usage and examples.

Why?

Because of End of Support of Vue2 is introducing CVE which can't be solved unless we remove the Vue 2 support. GHSA-g3ch-rx76-35fx

Removal of Vue 2 support:

• Deleted all Vue 2 example projects and related files, including examples/vite-vue2 and examples/vue-cli-vue2, along with their configuration, source, and documentation files. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15]
• Removed Vue 2 from the list of supported frameworks in the documentation and updated all related instructions and references in README.md and examples/README.md. [1] [2] [3] [4] [5]

Dependency and configuration updates:

• Removed vue2 compiler and all references to it from the core codebase (src/core/compilers/index.ts). [1] [2]
• Cleaned up peer dependencies in package.json by removing vue-template-compiler, vue-template-es2015-compiler, and Vue 2 compatibility for @vue/compiler-sfc. [1] [2]

Other maintenance:

• Updated pnpm-workspace.yaml with new dependency overrides (unrelated to Vue 2 removal, but included in this PR).

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​builder.io/​qwik@​1.2.10 ⏵ 1.18.0	+1	+2	-14
	react@​18.2.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm safer-buffer is 94.0% likely obfuscated Confidence: 0.94 Location: Package overview From: pnpm-lock.yaml → npm/[email protected] ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/unplugin-icons@430

commit: 7b8e713