Reviewing files that changed from the base of the PR and between 02d2f18 and 9e13314.

• integrations/ts-react16-overrides/package.json (1 hunks)
• integrations/ts4-react17/package.json (2 hunks)

• GitHub Check: npm:integrations/ts-react16-overrides on node 22.x
• GitHub Check: yarn:my-charts-react18:app-react18 on node 24.x
• GitHub Check: yarn:integrations/ts-react16 on node 24.x
• GitHub Check: yarn:my-charts-react18:app-react18 on node 22.x
• GitHub Check: npm:integrations/ts4-react17 on node 22.x
• GitHub Check: npm:integrations/ts-react18 on node 20.x
• GitHub Check: npm:integrations/ts-react16-overrides on node 20.x

integrations/ts4-react17/package.json (1)

34-41: Clarify the scope and necessity of the nested override syntax.

The nested override structure ("recharts": { ... }) applies only to packages when they are dependencies of recharts, but react and react-dom are direct dependencies in this package.json (lines 12-13) and therefore won't be correctly overridden by the scoped rule. For direct dependencies, use a flat override structure instead.

Additionally, web searches for npm changelog documentation show no breaking change in the overrides syntax between Node 22 and Node 24. The feature works to force compatible versions, but requires a clean install to apply properly and has had historical bugs where overrides are silently ignored. Clarify whether the issue is the syntax itself or whether a clean npm install and version validation resolved the Node 24 problem.

• Verify @reduxjs/toolkit and react-redux are only transitive dependencies of recharts; if not, move them to the flat override level.
• Confirm that a clean install with this configuration works in Node 24, and document the specific Node 24 incompatibility that was resolved.

integrations/ts-react16-overrides/package.json (1)

35-42: The scoped override syntax is valid, but clarify the actual Node 24 compatibility issue and redundant scoping.

The nested overrides structure is documented and valid npm syntax. However, the original concern about "breaking changes" in npm overrides syntax between Node 22 and 24 is incorrect. The actual issue is that Node 24 ships with npm v11 (which has different lockfile validation and overrides behavior compared to earlier npm versions), and upgrading Node requires regenerating the package-lock.json to match the new npm version's resolution.

Additionally, react and react-dom are direct dependencies (lines 14–15), so overriding them globally at the root level is appropriate. Scoping these overrides under the "recharts" key (lines 36–42) means they only override when recharts requests them—but since react and react-dom are also direct deps with identical versions, this scoping is partially redundant. Consider either:

1. Moving react and react-dom out of the recharts scope and into the root overrides (if you want them globally pinned), or
2. Documenting why the recharts-scoped override is necessary (e.g., if recharts' transitive dependencies conflict).

Ensure the package-lock.json was regenerated under Node 24 / npm v11 to avoid install/CI failures due to lockfile drift.