chore: upgrade recharts in www#6598
Conversation
WalkthroughThe recharts dependency is updated from ^3.3.0 to ^3.4.0 in the www package configuration, allowing installations to use the latest compatible minor version of the charting library. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes
Possibly related PRs
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
www/package.json(1 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: CR
Repo: recharts/recharts PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-10-25T07:36:02.229Z
Learning: Recharts aims for simple, declarative, and composable charts; prioritize consistency, usability, performance, and accessibility
📚 Learning: 2025-10-25T07:36:02.229Z
Learnt from: CR
Repo: recharts/recharts PR: 0
File: AGENTS.md:0-0
Timestamp: 2025-10-25T07:36:02.229Z
Learning: Recharts aims for simple, declarative, and composable charts; prioritize consistency, usability, performance, and accessibility
Applied to files:
www/package.json
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
- GitHub Check: Build, Test, Pack
- GitHub Check: Analyze (javascript-typescript)
| "react-router-dom": "^7.9.5", | ||
| "react-runner": "^1.0.5", | ||
| "recharts": "^3.3.0", | ||
| "recharts": "^3.4.0", |
There was a problem hiding this comment.
🧩 Analysis chain
Straightforward minor version bump; verify compatibility with 3.4.0 changes.
The dependency upgrade from ^3.3.0 to ^3.4.0 is reasonable and uses consistent versioning patterns. However, ensure that any breaking changes or behavioral differences in recharts 3.4.0 are compatible with the website code.
To verify compatibility, check the recharts 3.4.0 release notes for any breaking changes or significant behavioral updates:
Additionally, run the website build and manual smoke tests to confirm the upgrade doesn't introduce regressions.
🌐 Web query:
What are the breaking changes in recharts 3.4.0?
💡 Result:
I couldn't find a Recharts v3.4.0 release or changelog — the official releases page lists up through v3.3.0. [1]
If you meant the major 3.0 breaking changes (common when jumping to 3.x), key breaking items are: CategoricalChartState removed; no longer receives internal Recharts props; many internal-only props removed (e.g., points, payload, activeIndex); removal of some deprecated props (e.g., alwaysShow on Reference components) and removal of ref.current.current in ResponsiveContainer. See the 3.0 migration guide for the full list. [2]
Sources:
- Recharts releases (shows latest v3.3.0). [1]
- Recharts 3.0 migration guide / breaking changes. [2]
Critical Issue: Recharts version 3.4.0 does not exist in npm registry.
The latest available version of recharts is 3.3.0 as of November 2025. The package.json change specifies ^3.4.0, which cannot be resolved by npm/yarn. This will cause the dependency installation to fail.
Change the version to an existing release: either keep ^3.3.0 or upgrade to a published version within the 3.x series (e.g., ^3.3.0 if current, or verify against the available releases).
🤖 Prompt for AI Agents
In www/package.json around line 45, the dependency entry pins "recharts":
"^3.4.0" which doesn't exist in the npm registry and will break installs; change
the version string to a published release (for example "^3.3.0") or confirm and
use a valid 3.x version available in the registry, then run npm/yarn install to
verify resolution.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6598 +/- ##
=======================================
Coverage 94.57% 94.57%
=======================================
Files 491 491
Lines 40697 40697
Branches 4771 4771
=======================================
Hits 38491 38491
Misses 2201 2201
Partials 5 5 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Bundle ReportBundle size has no change ✅ |
1 participant
upgrade recharts in the website
Summary by CodeRabbit