Koa v3 Tracker

[jonathanong]

Starting a new tracker for v3

Milestone: https://github.com/koajs/koa/milestone/4

Other Breaking Changes:

• [ ] rewrite to ES modules
• [ ] adjust naming to WHATWG standards https://nodejs.org/api/url.html#url_url_strings_and_url_objects
• [ ] rename raw http requests? https://github.com/koajs/koa/issues/1114#issuecomment-405937240
• [ ] officially support the http2 module

Tests:

• [x] Migrate to jest
• [x] Properly close down server after each test run

Improved Documentation:

• [x] how to serve http/https/http2
• [ ] example of how to use expect-continue
• [ ] https://github.com/koajs/koa/discussions/1827
• [x] https://github.com/koajs/koa/discussions/1774 SSE example with AI chat

[jaydenseric]

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:

https://github.com/jaydenseric/coverage-node

[talentlessguy]

to add, Node test runner has identical API to Jest

for assertion, node:assert could be used

[benmccann]

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)

[jonathanong]

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

[iietmoon]

We are in love in koa, and such good thing we go with roadmap for v3 and contribute for fixing some issues, since we work too in our web framework "Mavro" and Koa has big hand on core of it, if someone want to contribute will be good to go with us https://discord.gg/jJK5kZx84B