refactor: drop jest#2
Open
slagiewka wants to merge 1 commit into
Open
Conversation
In modern node projects, the stdlib is usually enough. In other cases, other testing frameworks provide better interop with TypeScript and/or ES modules. Bump tsx to the latest version to rid of warnings on node 26. Tested on latest 18, 20, 22, 24, 26.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hey, I'm following this project from the thread in
graphql-js😉I thought I might leave this in case the project gets more traction. Even such a simple suite of tests suffers under Jest.
Execution time:
Before: 1.4-2s
After: 200-300ms
It might be even faster if
tsxis not needed - with node's native type erasing.In modern node projects, the stdlib is usually enough. In other cases, other testing frameworks provide better interop with TypeScript and/or ES modules.
Bump tsx to the latest version to rid of warnings on node 26.
Tested on latest 18, 20, 22, 24, 26.
It's totally OK if you have other goals in mind or this doesn't fit the project.