Hacker News Reader

YES. It was such a joy to be able to ditch Jest completely and run tests natively.

i tried that but had to revert to vitest, the native test runner feels incomplete atm.

What is missing for your use case or workflow?

Probably a bunch of assertion types and general DX. Node:test is just a feature, Vitest is a whole product. The former might be enough for small packages but nowhere near useful for anything non-trivial.

Fair enough. We still use Jest at work for exactly those reasons. In my personal projects, I prefer to minimise dependencies rather than get every DX benefit I can.

for instance exiting the runner on the first error. and the diffs with node:assert are not as nice either compared to vitest.

i'm building a framework with minimal dependencies at https://www.plainweb.dev so i'm super excited about everything that node builds in (sqlite, typescript).

but there is a difference between supporting the bare minimum and actually making it nice to use day to day.

Reply on news.ycombinator.com