Improve bundle size chart to show differences between versions #37
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.
The bundle size chart now displays the differences between consecutive versions instead of absolute values, making it much easier to see actual changes between Rolldown versions.
Problem
The original bundle size chart showed absolute values (e.g., 571,470 bytes vs 571,458 bytes) which made it extremely difficult to see the actual changes between versions. Users had to manually calculate differences to understand performance improvements or regressions.
Solution
Transformed the bundle size data to show differences between consecutive versions with enhanced visual indicators:
Example
With the test data, the chart now clearly shows:
This makes it immediately obvious that v7.1.3 had the most significant bundle size improvement, which was invisible in the original absolute value chart.
Fixes #36.
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.