Repository navigation
feat: upgrade Yuku to 0.18.0 and adapt integrations - #1288
Conversation
Merging this PR will improve performance by 61.29%
|
| Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|
| ⚡ | npm-wrapper/config-discovery/cached-1000-inputs |
12.4 ms | 7.5 ms | +66.66% |
| ⚡ | npm-wrapper/native-flat-config/1000-files |
299 ms | 179.7 ms | +66.35% |
| ⚡ | npm-wrapper/config-discovery/uncached-1000-inputs |
163.4 ms | 98.9 ms | +65.26% |
| ⚡ | utoo-lint/fixtures/codspeed |
187.7 ms | 118.7 ms | +58.15% |
| ⚡ | npm-wrapper/umi-severity-config/1000-files |
281.3 ms | 186.7 ms | +50.66% |
Tip
Curious why performance improved? Comment @codspeedbot explain why performance improved on this PR, or directly use the CodSpeed MCP with your agent.
Comparing zoomdong/update-yuku-0.18.0 (b3c9f28) with main (c03bddd)
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Summary
Upgrade the vendored Yuku parser and npm
yuku-parserfrom 0.10.1 to 0.18.0, keeping the native engine, ESLint plugin parser, and Playground AST inspector aligned.no-shadow,no-unused-vars, andno-use-before-definebehavior for signature parameters, import aliases, and type-only exports.yuku-parserwith asynchronous@yuku-core/wasminitialization, including dependency pins and deployment asset checks.Validation
Performance validation
CodSpeed's performance gate passes. The hosted walltime report warns about unknown/different execution environments, so its reported improvements should not be attributed to this upgrade. An unchanged-main control run under the current toolchain also increased versus the historical baseline.
A same-host differential check using pinned ReleaseFast builds and Node 24 validates each 1,000-file report: 120 alternating severity pairs average 485.52 ms on main versus 480.22 ms here (head/base 95% interval 0.959–1.019), and 40 native flat-config pairs average 571.27 ms versus 566.96 ms (0.966–1.017). These do not reproduce the earlier walltime alerts on macOS arm64; Linux hosted-runner measurements remain sensitive to environment differences.