Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (4)
💤 Files with no reviewable changes (1)
📝 WalkthroughWalkthroughVite and related plugin dependencies are upgraded across benchmark package configurations, with version overrides removed from the root pnpm configuration. Updates include Vite from 7.3.1 to 8.0.0, Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
Comment |
|
View your CI Pipeline Execution ↗ for commit 34d1a58
☁️ Nx Cloud last updated this comment at |
🚀 Changeset Version Preview1 package(s) bumped directly, 3 bumped as dependents. 🟩 Patch bumps
|
Bundle Size Benchmarks
Trend sparkline is historical gzip bytes ending with this PR measurement; lower is better. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 25e057fdeb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "typescript": "^5.7.2", | ||
| "vite": "^7.3.1", | ||
| "vite-plugin-solid": "^2.11.10" | ||
| "vite": "^8.0.0", |
There was a problem hiding this comment.
Reset bundle-size history when switching fixtures to Vite 8
If the existing benchmarks/bundle-size dashboard/history is kept, this changes the benchmarked bundler from Vite 7/Rollup to Vite 8/Rolldown. The bundle-size pipeline still publishes under the unchanged Bundle Size (gzip) series and scenario IDs (scripts/benchmarks/bundle-size/measure.mjs, .github/workflows/bundle-size.yml), so the first post-migration PR/main runs will compare Rolldown output against old Rollup data and report synthetic regressions/improvements unrelated to router changes.
Useful? React with 👍 / 👎.
Merging this PR will degrade performance by 13.55%
Performance Changes
Comparing |
Summary
pnpm-lock.yamlso the benchmark importers resolve to Vite 8 and drop the old Vite 7-only transitive entriesTesting
pnpm installCI=1 NX_DAEMON=false pnpm nx run @benchmarks/bundle-size:build --outputStyle=stream --skipRemoteCacheCI=1 NX_DAEMON=false pnpm nx run @benchmarks/client-nav:test:perf --outputStyle=stream --skipRemoteCacheCI=1 NX_DAEMON=false pnpm nx run @benchmarks/ssr:test:perf --outputStyle=stream --skipRemoteCacheCI=1 NX_DAEMON=false pnpm test:eslintCI=1 NX_DAEMON=false pnpm test:typesCI=1 NX_DAEMON=false pnpm test:unitSummary by CodeRabbit