Testing Next.js with Vitest (without next/jest) — any gotchas?
Unanswered
California Condor posted this in #help-forum
California CondorOP
Does anyone know if there are issues with using Vitest to test Next.js components since it doesn’t use next/jest?
I know next/jest reads from next.config.js, so I’m wondering whether leaving it out could cause certain Next.js behaviors or expectations to break in tests.
I haven’t run into problems so far, but I’m curious if there are any known limitations or subtle issues I should be aware of.
Thanks in advance!
I know next/jest reads from next.config.js, so I’m wondering whether leaving it out could cause certain Next.js behaviors or expectations to break in tests.
I haven’t run into problems so far, but I’m curious if there are any known limitations or subtle issues I should be aware of.
Thanks in advance!