Open jonathanong opened 3 months ago
Regarding the goal to move to Jest; please don't. Use the native Node.js test runner! It should be more than adequate.
You can pair it with coverage-node
, a very lightweight CLI tool, to enforce 100% code coverage in tests:
to add, Node test runner has identical API to Jest
for assertion, node:assert
could be used
Vitest is another fairly lightweight option for jest-compatible test runner. My last experience was that Jest is terrible to use with ESM as it doesn't fully support it yet. vitest is much better in this regard.
A rewrite might also be a nice time to take a look at including only minimal dependencies (e.g. https://npmgraph.js.org/?q=koa vs https://npmgraph.js.org/?q=polka)
I just realized that I already migrated it to jest a while go haha. if anyone is interested in migrating to node's official test runner, that would be great. otherwise, I will leave it as is
Starting a new tracker for v3
Milestone: https://github.com/koajs/koa/milestone/4
Other Breaking Changes:
Future:
Tests:
Improved Documentation: