We switched from Jest to Vitest this summer as part of the effort to migrate a large node repository to ESM. Jest presented a lot of issues after switching to ESM. Vitest was compatible with our existing jest code, minus a couple altered method signatures. It was also compatible with custom matchers we had implemented with jest-extend.
Most of the migration effort was spent on configuration for our needs. Vitest is quite flexible so it was just a matter of nailing down what worked for us.
Fun bit of trivia for you: members of my family claim my great grandmother taught Earl Scruggs the finger roll technique he made famous. He was boyhood friends with my grandmother's brother and they would hang out and pick on the porch.
His wikipedia page suggests the technique was common in the area, so while she probably didn't teach it to him, there's probably a kernel of truth in there somewhere.
I remember my friend ripping this to a CD-ROM for me in high school (early 2000s). It included the tooling application for editing stuff like the parameters for environment generation. I had no idea what I was doing and it didn't run well on my family PC, but I consider it a pretty big milestone on the journey that led to me sitting here reading HN instead of figuring out why my unit tests are failing.
I know how you feel, and it took such a long time for me to recognize that the way my mind works is not necessarily the way everyone's works, and that I'm not inferior to anyone else because of it.
But you gotta admit sometimes it's a really fascinating place in there.
I work in a typescript environment and quokkaJS is my choice for a quick prototyping environment.