3 ms·

I think keeping it unsupported for a couple of years, and reluctantly pushing it off to volunteers who barely have enough technical experience to support it is

I think keeping it unsupported for a couple of years, and reluctantly pushing it off to volunteers who barely have enough technical experience to support it is quite close to "was killed". Until recently Jest had a bug that made it crash due to sl (yes, the famous steam locomotive) running under the hood. This gives a hint at, ahem, the sophistication of its architecture. The project is long in its EOL, and the only reason for its use is inertia, the jQuery kind of it.

boredtofears 1y ago
Any idea what people have generally moved on to? Currently using jest but its definitely showing its warts often and is pretty slow. Curious if there is an obvious successor.
- vermilingua 1y ago
  Vitest is the incumbent I would say, but there seems to be a lot of momentum behind the runtime-builtin test runners recently. Bun is gaining traction like nothing else, and node has put a lot of work into the test builtins lately.
  - hungryhobbit 1y ago
    Node's test runner is a non-contender, at least right now. If you've ever used any other test runner, you'll find Node's is woefully inferior. I'd say "but maybe it will get better", except I've seen the maintainer responses to several issues, and it seems they are wedded to bad architectural decisions that keep it that way.
    - runarberg 1y ago
      The node test runner is perfect for small libraries without build where you pretty much ship the source code. The assertion library is actually superior to vitest’s if you don’t use spies etc. because unlike vitest’s assertions, the node ones do type narrowing correctly.
- pavel_lishin 1y ago
  Vitest is what people have been suggesting to me.
- hungryhobbit 1y ago
  There's always Mocha.
- AstroBen 1y ago
  I've had a really good experience with vitest
- WorldMaker 1y ago
  I moved back to Mocha with Chai for a while (both have great ESM support, quietly still well maintained, despite predating Jest) and then to Node's built-in test harness (and Deno's), sometimes still using Chai rather than `node:assert/strict` or `jsr:@std/assert`. But I wasn't using a lot of Jest features anyway, generally preferred Mocha even during the height of Jest's popularity, and Node's test runner is sufficient for most of my needs (and Deno's starts to seem more and more the path forward as I come to prefer deno.json in a lot more types of projects than package.json).

boredtofears 1y ago

Any idea what people have generally moved on to? Currently using jest but its definitely showing its warts often and is pretty slow. Curious if there is an obvious successor.

vermilingua 1y ago
Vitest is the incumbent I would say, but there seems to be a lot of momentum behind the runtime-builtin test runners recently. Bun is gaining traction like nothing else, and node has put a lot of work into the test builtins lately.
- hungryhobbit 1y ago
  Node's test runner is a non-contender, at least right now. If you've ever used any other test runner, you'll find Node's is woefully inferior. I'd say "but maybe it will get better", except I've seen the maintainer responses to several issues, and it seems they are wedded to bad architectural decisions that keep it that way.
  - runarberg 1y ago
    The node test runner is perfect for small libraries without build where you pretty much ship the source code. The assertion library is actually superior to vitest’s if you don’t use spies etc. because unlike vitest’s assertions, the node ones do type narrowing correctly.
pavel_lishin 1y ago
Vitest is what people have been suggesting to me.
hungryhobbit 1y ago
There's always Mocha.
AstroBen 1y ago
I've had a really good experience with vitest
WorldMaker 1y ago
I moved back to Mocha with Chai for a while (both have great ESM support, quietly still well maintained, despite predating Jest) and then to Node's built-in test harness (and Deno's), sometimes still using Chai rather than `node:assert/strict` or `jsr:@std/assert`. But I wasn't using a lot of Jest features anyway, generally preferred Mocha even during the height of Jest's popularity, and Node's test runner is sufficient for most of my needs (and Deno's starts to seem more and more the path forward as I come to prefer deno.json in a lot more types of projects than package.json).