Replace Babel and esbuild with Yuku#40
Closed
hardfist wants to merge 4 commits into
Closed
Conversation
commit: |
Collaborator
|
Closing this in favor of #39, which now contains the Yuku parser/codegen work plus the broader route artifact/cache performance optimizations in a single PR. |
Member
|
Is Yuku production ready? It still looks like a very new project |
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.
Summary
This is an experimental test to test the perf gain
pnpm bench:yukuto compare the previous HEAD implementation with the current Yuku-backed implementation.Performance
Benchmark command:
pnpm bench:yukuValidation
pnpm buildpnpm test:corepnpm bench:yuku