refactor: migrate to vite-plus

[ibrunotome]

No description provided.

[cloudflare-workers-and-pages]

Deploying with Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	auth	a98d00c	Commit Preview URL Branch Preview URL	Aug 03 2026, 05:25 PM

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​voidzero-dev/​vite-plus-core@​0.2.4
	vite-plus@​0.2.4

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 oxfmt is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/vite-plus@0.2.4 → npm/oxfmt@0.57.0 ℹ 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/oxfmt@0.57.0. 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 oxfmt is 90.0% likely obfuscated Confidence: 0.90 Location:Package overview From:pnpm-lock.yaml → npm/vite-plus@0.2.4 → npm/oxfmt@0.57.0 ℹ 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/oxfmt@0.57.0. 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

[cubic-dev-ai]

1 issue found and verified against the latest diff

Confidence score: 5/5

• In pnpm-workspace.yaml, keeping both peerDependencyRules.allowedVersions for vite and peerDependencyRules.allowAny creates redundant policy that can confuse future dependency maintenance without changing behavior—remove allowedVersions: { vite: '*' } and keep allowAny only.

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="pnpm-workspace.yaml">
<violation number="1" location="pnpm-workspace.yaml:28">
P3: `peerDependencyRules.allowedVersions` for vite is redundant with `peerDependencyRules.allowAny` — both already allow any version of vite as a peer dependency. Drop `allowedVersions: { vite: '*' }` and keep only `allowAny: [vite]`, which is the cleaner path for blanket permission. If you later want a tighter range to surface unexpected version conflicts, swap to `allowedVersions` alone instead.</violation>
</file>

<sub>Heads up: you’re close to your included review allowance. Set a flex budget so reviews don’t pause.

Re-trigger cubic</sub>

[cubic-dev-ai]

P3: peerDependencyRules.allowedVersions for vite is redundant with peerDependencyRules.allowAny — both already allow any version of vite as a peer dependency. Drop allowedVersions: { vite: '*' } and keep only allowAny: [vite], which is the cleaner path for blanket permission. If you later want a tighter range to surface unexpected version conflicts, swap to allowedVersions alone instead.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At pnpm-workspace.yaml, line 28:
<comment>`peerDependencyRules.allowedVersions` for vite is redundant with `peerDependencyRules.allowAny` — both already allow any version of vite as a peer dependency. Drop `allowedVersions: { vite: '*' }` and keep only `allowAny: [vite]`, which is the cleaner path for blanket permission. If you later want a tighter range to surface unexpected version conflicts, swap to `allowedVersions` alone instead.</comment>
<file context>
@@ -18,3 +18,23 @@ allowBuilds:
+peerDependencyRules:
+ allowAny:
+ - vite
+ allowedVersions:
+ vite: '*'
+minimumReleaseAgeExclude:
</file context>