Skip to content

Update dependency recharts to v3#30

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/recharts-3.x
Open

Update dependency recharts to v3#30
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/recharts-3.x

Conversation

@renovate

@renovate renovate Bot commented Aug 11, 2025

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
recharts 2.15.03.8.1 age confidence

Release Notes

recharts/recharts (recharts)

v3.8.1

Compare Source

What's Changed

Bugfixes!

New Contributors

Full Changelog: recharts/recharts@v3.8.0...v3.8.1

v3.8.0

Compare Source

What's Changed

We added generics to our data and dataKey props and now you can have your charts validated by TypeScript. See the full guide here: https://recharts.github.io/en-US/guide/typescript/

We are releasing new helper functions and hooks that will allow you to precisely target mouse interactions, and convert coordinates. See the guide here: https://recharts.github.io/en-US/guide/coordinateSystems/

And new functions and hooks:

getRelativeCoordinate - converts mouse events to pixel positions

Convert Data → Pixels:

useXAxisScale - returns a function to convert X data values to pixel positions
useYAxisScale - returns a function to convert Y data values to pixel positions
useCartesianScale - convenience hook for converting both at once

Pixels → Data:

useXAxisInverseScale - returns a function to convert pixel X to the closest data value
useYAxisInverseScale - returns a function to convert pixel Y to the closest data value
useXAxisInverseTickSnapScale - returns a function to convert pixel X to the closest axis tick
useYAxisInverseTickSnapScale - returns a function to convert pixel Y to the closest axis tick

Accessing Ticks:

useXAxisTicks - returns the calculated ticks of an X-axis
useYAxisTicks - returns the calculated ticks of a Y-axis

Feat
Fix
Types
Docs

New Contributors

Full Changelog: recharts/recharts@v3.7.0...v3.8.0

v3.7.0

Compare Source

v3.6.0

Compare Source

What's Changed

3.6 🚀 - check out BarStack and ranged stacked bars 📊

Feat
Fix
Chore
  • CartesianAxis: Deprecate CartesianAxis @​PavelVanecek in #​6774
  • Bump to Node 24
  • Lots of undefined checks for progress towards TS strict mode
Docs
  • Docs should be improving on the daily - comments in code + storybook + the website should all be coming closer to in sync thanks to @​PavelVanecek pretty much writing his own documentation generator 🤖 🚀

New Contributors

Full Changelog: recharts/recharts@v3.5.1...v3.6.0

v3.5.1

Compare Source

What's Changed

Fix
  • Pie: add missing Sector index to Pie shape prop by @​ckifer in #​6683
    • This enables customization of specific slices of the Pie similar to activeIndex in 2.x
  • Pie: prevent cross-Pie highlighting in multi-Pie PieCharts with shared dataKeys by @​shreedharbhat98 in #​6678
    • Only marks a specific Sector as active when that sector is hovered
  • TypeScript/Tooltip: update activeLabel type to be a string | number by @​ckifer in #​6691
    • !! NOTE !!: This change may break your types if you relied on it as a string, but this is a bug fix
  • Accessibility/General: add tabIndex -1 on Recharts ZIndex svg portal g tags to prevent extraneous focusable surfaces by @​ckifer in #​6687
  • General: Removed accidental eslint dependency from main dependencies which should remove it from installation with recharts

New Contributors

Full Changelog: recharts/recharts@v3.5.0...v3.5.1

v3.5.0

Compare Source

What's Changed

Mostly fixes and performance improvements this release but check out the deprecation of Pie active/inactiveShape in favor of aligning with the shape prop of other chart elements.

Feat
  • Pie: add shape to align custom Pie sector shapes to other Recharts components by @​ckifer in #​6482
    • This change deprecates activeShape and inactiveShape. Please use the isActive prop passed from the callback to shape to create active Pie sectors.
    • Note: forgot to include the current Sector index, will add in 3.5.1
  • Stacked Charts: implement reverseStackOrder prop in v3 - fixes a regression between recharts 2 and 3 by @​j-shimizu111 in #​6644
  • Typescript/Dot: export ActiveDotProps and DotItemDotProps types by @​simaks in #​6657
Fix
Docs
New Contributors (thanks everyone!)

Full Changelog: recharts/recharts@v3.4.1...v3.4.2

v3.4.1

Compare Source

What's Changed

Forgot some exports for Z Index in 3.4

Full Changelog: recharts/recharts@v3.4.0...v3.4.1

v3.4.0

Compare Source

v3.3.0

Compare Source

What's Changed
Feat
  • ResponsiveContainer is now built-in to all charts by @​PavelVanecek in #​6388
    • add the responsive prop to any chart along with a height and width as if you were using ResponsiveContainer. One less component to wrap things with. ResponsiveContainer will continue to work for the life of 3.x
<BarChart data={data} responsive height={300} width="100%">
  ....
</BarChart>
Fix
Website changes - https://recharts.github.io/

Unfortunately the current contributors and admins do not own recharts.org and the renewal of the domain remains up in the air. To remove that uncertainty we have deployed the website at our github pages URL instead.

New Contributors

Full Changelog: recharts/recharts@v3.2.1...v3.3.0

v3.2.1

Compare Source

What's Changed
Fix
New Contributors

Full Changelog: recharts/recharts@v3.2.0...v3.2.1

v3.2.0

Compare Source

What's Changed

Quite a bit of 3.0 bug fixes in this release along with two new hooks. Thanks to all who've been reporting issues!

Feat
Hooks
Fix
Chore
New Contributors (thanks everyone!)

Full Changelog: recharts/recharts@v3.1.2...v3.1.3

v3.1.2

Compare Source

What's Changed

Fix

Full Changelog: recharts/recharts@v3.1.1...v3.1.2

v3.1.1

Compare Source

What's Changed

Fix
  • General: Don't apply duplicate IDs in the DOM by @​PavelVanecek in #​6111
  • Stacked Area/Bar: give all graphical items their own unique identifier and use that to select stacked data. Fixes issue where stacked charts could not be created from the graphical item data prop #​6073 by @​PavelVanecek
  • Stacked Area/Bar: exclude stacked axis domain when not relevant for axis by @​rinkstiekema in #​6162 fixes issue where numeric stacked charts would not render correctly
  • Area Chart: ranged area chart - show active dot on both points instead of just the top one by @​sroy8091 in #​6116 fixes #​6080
  • Polar Charts/Label: fix Label in polar charts by @​PavelVanecek in #​6126
  • Scatter/ErrorBar: choose implicit Scatter ErrorBar direction based on chart layout (to be the same as 2.x) by @​PavelVanecek in #​6159
  • X/YAxis/Reference Components: allow axis values and reference items to render when there is no data but there is a domain/explicit ticks set by @​ethphan in #​6161
  • X/YAxis: pass axis padding info to custom tick components by @​shreedharbhat98 in #​6163
Chore / Testing
  • good progress on our journey to enable strictNullChecks
  • addition of playwright visual regression tests to CI
  • split Animate into JavascriptAnimate and CSSTransitionAnimate by @​PavelVanecek in #​6175

New Contributors

Full Changelog: recharts/recharts@v3.1.0...v3.1.1

v3.1.0

Compare Source

What's Changed

Bug fixes (old and new) and a few new hooks post 3.0 launch!

Feat

More hooks!

Fix
  • Legend: After hiding and showing legend elements, keep them in the same order as before by @​PavelVanecek in #​6026
  • Bar: add payload as a valid property on BarRectangleItem by @​ckifer in #​6029
  • Accessibility: Remove role=application from recharts wrapper (this was removed in 2.x for accessibility reasons) by @​PavelVanecek in #​6060
  • ResponsiveContainer: Add overflow: visible zero-size wrapper so that ResponsiveContainer can shrink by @​PavelVanecek in #​6068
  • X/YAxis: Fix tickCount and allowDecimals if axis domain does not include the keyword 'auto' by @​PavelVanecek in #​6070
  • Tooltip: Fix active tooltip and dots when there are multiple graphical items each with their own data by @​PavelVanecek in #​6074
Docs
Chore

New Contributors

Full Changelog: recharts/recharts@v3.0.2...v3.1.0

v3.0.2

Compare Source

What's Changed

Please skip 3.0.1 and go straight to 3.0.2 - #​6022. In React.StrictMode charts in 3.0.1 were not rendering at all. This revert should resolve that.

Full Changelog: recharts/recharts@v3.0.1...v3.0.2

v3.0.1

Compare Source

⚠️ Version 3.0.1 has a bug where some charts will not render in React strict mode. Please use 3.0.2 or higher. ⚠️

What's Changed

Lots of fixes from the 3.0 release - thanks for the reports!

Edit: broke something #​6022

Fix
  • Label: fix an issue which caused labelRef to get passed to custom DOM elements which logged an error/warning by @​saurabhraj123 in #​6008
  • Pie->Label: fix issue where pie labels were not rendering correctly when specified as a child of Pie by @​PavelVanecek in #​5987
  • Legend: apply legend itemSorter for custom content as well as default content by @​PavelVanecek in #​6012
    * Legend: keep legend items in the same order when they are hidden and shown by @​PavelVanecek in #​6017
  • Bar->Brush: fix undefined access error when using Brush with stacked bar charts by @​PavelVanecek in #​6009
  • X/YAxis: fix DecimalError when creating vertical oriented charts with a single datapoint by @​ckifer in #​6016
  • X/Y/PolarAngle/PolarRadius Axis: tickFormatter is no longer called with data indexes before the actual data by @​PavelVanecek in #​6019

Full Changelog: recharts/recharts@v3.0.0...v3.0.1

v3.0.0

Compare Source

🚀 Recharts 3 is here!

Huge shoutout to @​PavelVanecek who wrote 95% of the code for this major version release. We re-wrote recharts state management, wrote some 3500 unit tests, fixed a bunch of bugs, and added a few well-requested features.

The intent with 3.0 is that it is now a better/easier place for the community to contribute to. Looking forward to what the future of recharts looks like in 3.x and beyond!

More details and the 3.0 migration guide

BREAKING CHANGES

Please see https://github.com/recharts/recharts/wiki/3.0-migration-guide#breaking-code-changes

tldr;

  • CategoricalChartState (which was access to recharts internal state) no longer exists in event handlers or Customized, etc.
  • <Customized /> no longer receives recharts state/props
  • Removal of internal props that were always supposed to only be internal to recharts
  • Remove previously deprecated props
  • ...see full list linked above
New Features
  • Custom Components - you can now render any react component in the recharts tree structure (but it must still be renderable within an SVG). Previously this was controlled and filtered by recharts
  • Tooltip Portals - you can now use portals to position your tooltip data anywhere you'd like, including outside of your chart
  • Legend Portals - similar to the above, you can now use portals to position your Legend anywhere you'd like, including outside of your chart
  • Accessible by default - accessibilityLayer is now on on all polar and cartesian charts by default. Tab into the chart and use the arrow keys to navigate.
  • Polar charts now support multiple axes (similar to cartesian charts)
  • Tooltip: You can now select which axis your Tooltip belongs to using axisId
  • YAxis: auto width calculation for YAxes - set width="auto"
  • X/YAxis: Add symlog d3 scale type
Bug fixes and improvements

This release fixes some long standing issues in recharts, the easiest way to determine all of them is to take a look at the recharts 3.0 project board

  • Animation improvements
  • Typescript improvements
  • Accessibility fixes/improvements
  • Pie: no more border around pie sectors on click, etc.
  • CartesianGrid: background now renders below the grid lines instead of above
  • and more!

Our 3.0 storybook has a lot of updated examples!

v2.15.4

Compare Source

What's Changed

Last 2.x patch - releasing since the @babel/runtime vulnerability is showing up in some security scans. Hoping to release 3.0 on 6/22 🚀

Fix
  • X/YAxis: fix issue where recharts class names did not get passed to custom tick components by @​MyungAe in #​5840
  • Bar: allow minPointSize function to receive null and undefined values by @​eino in #​5947
  • TypeScript: fix issue which caused build errors when allowSyntheticDefaultImports: false by @​tfaller in #​5810
Security
  • resolve @​babel/runtime ReDoS vulnerability (SNYK-JS-BABELRUNTIME-10044504) by @​moehaje in #​5969
    • recharts isn't vulnerable to this per-se, but it does show up in security tooling like snyk

New Contributors

Full Changelog: recharts/recharts@v2.15.3...v2.15.4

v2.15.3

Compare Source

Last patch release before 3.0 🚀

What's Changed

Fix
  • XAxis: fix padding calculation for padding="gap" and padding="no-gap" when XAxis is type number by @​jackfletch in #​5759

Full Changelog: recharts/recharts@v2.15.2...v2.15.3

v2.15.2

Compare Source

What's Changed

Few bugfixes and bug fix backports for 2.x

Fix
  • Bar/Rectangle: add index back to Bar Rectangle key to prevent duplicate key issues by @​ckifer in #​5561
  • Dot: re-include points object in dotProps by @​brodriguezmilla in #​5657
  • Tooltip: add SVGProps to Tooltip payload type to account for svg properties such as opacity passed by the user by @​ally1002 in #​5712
  • Tooltip/Bar: fix activeBar prop not working when tooltip shared={false} by @​nizans in #​5718
  • General: allow data-* props to be spread on svg elements and not be filtered out by @​prtmwrkr in #​5666

New Contributors

Full Changelog: recharts/recharts@v2.15.1...v2.15.2

v2.15.1

Compare Source

What's Changed

Quick patch release, nothing crazy going on here.

In the meantime please help us test recharts 3.0 alpha #​5445 🚀

Fix
Chore

New Contributors

Full Changelog: recharts/recharts@v2.15.0...v2.15.1


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@vercel

vercel Bot commented Aug 11, 2025

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
whale-manager Error Error Jun 11, 2026 3:09pm

@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from bc62510 to a70034e Compare August 13, 2025 15:32
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from a70034e to 01b8e1b Compare August 19, 2025 18:43
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from 01b8e1b to a3a5f4f Compare September 1, 2025 02:10
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from a3a5f4f to 153cc5a Compare September 9, 2025 01:46
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from 153cc5a to d8c5e28 Compare September 16, 2025 13:36
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from d8c5e28 to 33ae71d Compare September 25, 2025 21:37
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from 33ae71d to b9d8859 Compare October 17, 2025 06:27
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from b9d8859 to fd55c5a Compare October 21, 2025 16:45
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from fd55c5a to c200188 Compare November 10, 2025 10:44
@socket-security

socket-security Bot commented Nov 10, 2025

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @libsql/client-wasm is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/@libsql/client-wasm@0.17.3

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@libsql/client-wasm@0.17.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm @prisma/client is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/@prisma/client@7.8.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@prisma/client@7.8.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
License policy violation: npm bcryptjs under BSD-3-Clause-HP

License: BSD-3-Clause-HP - The applicable license policy does not permit this license (5) (package/LICENSE)

From: package.jsonnpm/bcryptjs@3.0.3

ℹ Read more on: This package | This alert | What is a license policy violation?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Find a package that does not violate your license policy or adjust your policy to allow this package's license.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/bcryptjs@3.0.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm better-sqlite3 is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/better-sqlite3@12.10.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/better-sqlite3@12.10.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm drizzle-orm is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/drizzle-orm@0.45.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/drizzle-orm@0.45.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm immer is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/recharts@3.8.1npm/immer@11.1.8

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/immer@11.1.8. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from 1fc616a to 9836885 Compare February 2, 2026 20:00
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from 9836885 to c2e0664 Compare February 12, 2026 11:55
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from c2e0664 to fafd31a Compare February 17, 2026 17:39
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from fafd31a to dfd22f5 Compare March 5, 2026 15:43
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from dfd22f5 to e681509 Compare March 6, 2026 22:18
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from e681509 to 544cb98 Compare March 13, 2026 15:05
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from 544cb98 to cbecf0e Compare March 31, 2026 10:43
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from cbecf0e to 4b2b765 Compare April 1, 2026 16:43
@renovate renovate Bot changed the title fix(deps): update dependency recharts to v3 Update dependency recharts to v3 Apr 8, 2026
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from 4b2b765 to a1332a4 Compare April 8, 2026 16:46
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from a1332a4 to b125644 Compare April 29, 2026 20:51
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from b125644 to f6ed698 Compare May 12, 2026 09:41
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from f6ed698 to b440e75 Compare May 18, 2026 09:29
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from b440e75 to 1d6c19e Compare May 28, 2026 21:14
@renovate renovate Bot force-pushed the renovate/recharts-3.x branch from 1d6c19e to 9b1d9e2 Compare June 1, 2026 20:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants