-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Koa v3 Tracker #1837
Comments
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 |
to add, Node test runner has identical API to Jest for assertion, |
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 |
## Checklist use `node --test` instead of `jest` See: #1837 (comment) - [X] I have ensured my pull request is not behind the main or master branch of the original repository. - [X] I have rebased all commits where necessary so that reviewing this pull request can be done without having to merge it first. - [X] I have written a commit message that passes commitlint linting. - [X] I have ensured that my code changes pass linting tests. - [X] I have ensured that my code changes pass unit tests. - [X] I have described my pull request and the reasons for code changes along with context if necessary.
Starting a new tracker for v3
Milestone: https://github.com/koajs/koa/milestone/4
Other Breaking Changes:
Future:
Tests:
Improved Documentation:
The text was updated successfully, but these errors were encountered: