Replace benchmark.js with vitest bench
#793
Merged
Conversation
This file contains 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
hackerwins
force-pushed
the
vitest-bench
branch
2 times, most recently
from
658ca01 to
c12131d
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #793 +/- ##
==========================================
+ Coverage 80.24% 80.28% +0.04%
==========================================
Files 59 59
Lines 4439 4439
Branches 898 898
==========================================
+ Hits 3562 3564 +2
+ Misses 613 612 -1
+ Partials 264 263 -1 ☔ View full report in Codecov by Sentry. |
hackerwins
force-pushed
the
vitest-bench
branch
from
c12131d to
7c3f26e
Compare
hackerwins
changed the title
vitest bench
hackerwins
changed the title
vitest benchbenchmark.js with vitest bench
2 tasks
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.
What this PR does / why we need it?
Replace benchmark with vitest
Any background context you want to provide?
What are the relevant tickets?
Fixes #
Checklist