chore: update vite in e2e tests to ^8.1.0

[wan9chi]

Summary

Updates the pinned vite dependency for e2e tests from a specific commit hash to a stable version range (^8.1.0), now that the vite-task-client tests are performed with an official Vite release.

Changes

• Replaced the temporary commit-pinned vite dependency (https://pkg.pr.new/vite@1298951ebc5e5a94164c21f142fe748ca37eea68) with a standard version constraint (^8.1.0)
• Updated the accompanying comment to reflect that the integration is now available in a tagged release, removing the note about tracking main until release

Motivation

The vite-task-client integration was previously only available in the Vite main branch, requiring a pinned commit hash. Now that it has been merged and released in Vite 8.1.0+, we can use a normal semantic version range, which is more maintainable and allows for automatic patch/minor updates.

https://claude.ai/code/session_01GhRBzHrF7FjwBC7k2bd689

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​vite@​8.1.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 @emnapi/runtime is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/vite@8.1.0 → npm/@emnapi/runtime@1.11.1 ℹ 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 support@socket.dev. 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/@emnapi/runtime@1.11.1. 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