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
I was actually anticipating a "why vitest over bun?" question more than this haha.
To put it simply, jest is a far older, much slower and doesn't natively support ESM, which the monorepo is only ESM and so vitest would be much easier there, plus we also have packages/config/vite so we are all in on the vite ecosystem (outside of nextjs i guess) anywho I would actually even be interested in a bun:test implementation because that is the fastest unit testing framework out there currently and orbitkit should access newness with stability and functionality when a decision is made that's why i think vitest strikes that perfect balance between speed (bun) and stability (jest)
Activity
imCorfitz commentedon Apr 6, 2024
Why vitest over Jest? Just curious.
ixahmedxi commentedon Apr 6, 2024
I was actually anticipating a "why vitest over bun?" question more than this haha.
To put it simply, jest is a far older, much slower and doesn't natively support ESM, which the monorepo is only ESM and so vitest would be much easier there, plus we also have
packages/config/viteso we are all in on the vite ecosystem (outside of nextjs i guess) anywho I would actually even be interested in a bun:test implementation because that is the fastest unit testing framework out there currently and orbitkit should access newness with stability and functionality when a decision is made that's why i think vitest strikes that perfect balance between speed (bun) and stability (jest)duttaoindril commentedon Apr 29, 2024
let me do you the honors:
why vitest over bun:test??
ixahmedxi commentedon Apr 29, 2024
Actually I don't mind any, I think both are great