Migrating to Vitest about next-js-boilerplate HOT 8 CLOSED

Official Nextjs example code : https://github.com/vercel/next.js/tree/canary/examples/with-vitest

from next-js-boilerplate.

Why Vitest?

Next.js has a built-in configuration for Jest, which is not the case with Vitest if not wrong?

I can understand we can use Vitest with Vite but Next.js is not build on top of Vite. Love to hear any feedback and suggestion.

What bring Vitest compared to Jest?

from next-js-boilerplate.

https://vitest.dev/guide/comparisons.html#jest

Mainly for performance reasons, faster test suits means faster feedback loop which means improved DX.

There will be official Vite support in Nextjs probably when they reached 1.0

from next-js-boilerplate.

The default configuration provided by Next.js for Jest use @swc/jest behind the scene, should provide a good performance.

Based on some reddit post, Vitest is even slower: https://www.reddit.com/r/reactjs/comments/1066fvv/test_runner_spa_vite_react_vitest_vs_jestswc/?rdt=41518

from next-js-boilerplate.

Here is another post about the performance: https://www.jameslmilner.com/posts/speeding-up-typescript-jest-tests/

from next-js-boilerplate.

The default configuration provided by Next.js for Jest use @swc/jest behind the scene, should provide a good performance.

You may be probably right, sorry I did not considered the SWC,

Most recent bench mark without SWC integration shows it is just marginally faster, probably new Turbo pack will improve the test performance more with Jest or bring a testing capabilities like Bun.

So I'll close this issue!

from next-js-boilerplate.

@kaushalyap Thank you for your suggestion, always open to feedback and suggestion.

I would totally reconsider Vitest in the future, very promising.

from next-js-boilerplate.