Moving to vitest
from jest
#231
Closed
zrosenbauer
started this conversation in
Ideas
Replies: 2 comments 9 replies
-
I've heard great things about Vitest and definitely see the appeal. Really appreciate you bringing this up. it's a valuable discussion. It feels like an awesome improvement we should absolutely consider. Maybe we can revisit it after we’ve shipped basic workflow support and improved the DX around our TypeScript types. |
Beta Was this translation helpful? Give feedback.
9 replies
-
closing as resolved in #250 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Move to
vitest
as core testing framework forVoltAgent
Why
Better feature set
any
anymore (https://vitest.dev/guide/testing-types.html#testing-types)rust
module tests): (https://vitest.dev/guide/in-source)describe.todo
: I see a lot of comments to add tests but no way to surface them (https://vitest.dev/api/#describe-todo)Full list: https://vitest.dev/guide/features
Compatible with
jest
vitest
was built to be API compatible withjest
(https://vitest.dev/guide/migration.html#jest) and the migration should not be difficult to do.Intertia
The
nodejs
&typescript
community seems to be adopting it:ai
: https://github.com/vercel/ai/blob/main/packages/ai/vitest.node.config.jshono
: https://github.com/honojs/hono/blob/main/vitest.config.tsWhy Not?
Time
This is a non-feature add and more about DX working on the VoltAgent platform.
vite
withoutvitest
We aren't using
vite
for builds and that is one of main reasons to use it (or at least it was!)How
We could achieve this in pieces by creating a project to migrate, and any new packages added can be vitest.
@omeraplak FYI I'm willing to take lead on this too, but will have to be a weekend project for sure.
Beta Was this translation helpful? Give feedback.
All reactions