Establish TypeScript 5 CI benchmark baseline - #32
Open
mainframev wants to merge 15 commits into
Open
Conversation
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
1 participant
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.
Summary
Creates the TypeScript 5.7.3 comparison build for the TypeScript 6 migration in #31. This branch starts from the same base commit (
838a28171b) and keeps the upstream compiler version below 6.type-checktargets with Nx cache disabled and parallelism fixed at 4Comparison
Compare the
TypeScript benchmark / type-checkjob in this PR against the same job in #31. Both jobs useubuntu-latest, Node 22, four-way Nx parallelism, and an uncached full-workspace type-check.Preliminary local result on the same machine:
TypeScript 6 was 8s (2.1%) faster in the local run. GitHub-hosted results are the authoritative comparison.
This is a fork-only benchmark PR and is not intended for upstream merge.