Im an unfortunate soul. I’m a long time Vite and Vitest fan, but in a monorepo with React and React Native, it is impossible to use Vite/Vitest, unless you are willing to repeat utility code
@emirmarat66959 ай бұрын
thanks for a video!
@js2brain8 ай бұрын
My pleasure!
@dmitrygladkikh8230 Жыл бұрын
HappyDom option instead of jsdom seems interesting. Have you had an experience of using strykerjs in conjunction with vitest? I had a combination of karma + tsloader + webpack + stryker/karma. And it worked with an appropriate speed+-. Switching to vitest + stryker/vitest increased the execution time twice. But it is still better when stryker/jest + jest + tsjest/@swc/jest
@js2brain Жыл бұрын
I didn't use strykerjs yet. Looks like an interesting tool, though! 👍 Not sure how performance changes for vitest by using it, so maybe it makes sense to switch to happy-dom and take jsdom out of the equation. Another approach could be comparing vitest to jest using strykerjs on a node/isomorphic environment.
@milon27 Жыл бұрын
hi in one folder all of my test file are running parallel , so for testing database conflict data and failed many test. but when I run one file at a time all test are passing. how are configure vitest in a way so that it only run one testfile at a time?
@js2brain Жыл бұрын
Hey, the --threads flag might help: vitest.dev/config/#threads