[WIP] Fix incorrect path for Vitest configuration file

[Copilot]

Thanks for asking me to work on this. I will get started on it and keep this PR's description up to date as I form a plan and make progress.

Original prompt

The Performance Benchmark GitHub Actions job fails due to an incorrect path for the Vitest configuration file. The error indicates that the config file is being looked for at packages/vest/packages/vest/vitest.config.ts, but it should instead be packages/vest/vitest.config.ts.

To resolve this, find and update any reference to "packages/vest/packages/vest/vitest.config.ts" in project scripts, package.json, or GitHub workflow files (especially .github/workflows/benchmark.yml) to instead use "packages/vest/vitest.config.ts".

Test the fix by ensuring the workflow launches and the config file is picked up properly, resolving the "Could not resolve vitest.config.ts" error.

This pull request was created as a result of the following prompt from Copilot chat.

The Performance Benchmark GitHub Actions job fails due to an incorrect path for the Vitest configuration file. The error indicates that the config file is being looked for at packages/vest/packages/vest/vitest.config.ts, but it should instead be packages/vest/vitest.config.ts.

To resolve this, find and update any reference to "packages/vest/packages/vest/vitest.config.ts" in project scripts, package.json, or GitHub workflow files (especially .github/workflows/benchmark.yml) to instead use "packages/vest/vitest.config.ts".

Test the fix by ensuring the workflow launches and the config file is picked up properly, resolving the "Could not resolve vitest.config.ts" error.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
vest	Ready	Preview	Comment	Nov 27, 2025 5:24pm
vest-next	Error			Nov 27, 2025 5:24pm