You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cypress should've already migrated to Vitest. I understand it's been around for a long time and a lot of codebases rely on Mocha and Chai, making the update challenging. However, offering Vitest as an opt-in option in the Cypress configuration would be highly beneficial.
Why is this needed?
Integrating Cypress with projects that already use Vitest would simplify development and eliminate the need to manage ESLint rules for Mocha and Chai. A unified, modern, and fast tool like Vitest would enhance the DX compared to the older combination of Mocha and Chai. In addition, having a dedicated vitets.config.ts file for configuration would streamline the setup process.
Other
No response
The text was updated successfully, but these errors were encountered:
What would you like?
Cypress should've already migrated to Vitest. I understand it's been around for a long time and a lot of codebases rely on Mocha and Chai, making the update challenging. However, offering Vitest as an opt-in option in the Cypress configuration would be highly beneficial.
Why is this needed?
Integrating Cypress with projects that already use Vitest would simplify development and eliminate the need to manage ESLint rules for Mocha and Chai. A unified, modern, and fast tool like Vitest would enhance the DX compared to the older combination of Mocha and Chai. In addition, having a dedicated vitets.config.ts file for configuration would streamline the setup process.
Other
No response
The text was updated successfully, but these errors were encountered: