Upgrading victory-pie from 37.x to 38.x

Comparison of the public API of victory-pie 37.4.1 and 38.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths	0
Removed exports	0
Changed signatures	1
Removed class or interface members	0
Changed class or interface members	0
Newly deprecated	0
Requirement changes (engines, peer dependencies)	1
New exports	0

Removed exports

None detected.

Changed signatures

export	Before	After
`victory-pie · VictorySliceLabelPositionType`	`"startAngle" \| "centroid" \| "endAngle"`	`"endAngle" \| "startAngle" \| "centroid"`

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

	Before	After
`peerDependencies.react`	`>=16.6.0`	`>=18`

Changelog between these versions

Text published by the package authors, shown as-is.

38.0.0

### Major Changes

- [#3138](https://github.com/FormidableLabs/victory/pull/3138) [`b7ebc3e`](https://github.com/FormidableLabs/victory/commit/b7ebc3e316d05740f11d4e8b8072d420db6ccfad) - Require React 18 or later: the `react` peer dependency is now `>=18` (was `>=16.6.0`). If you're on React 16 or 17, stay on Victory 37.x until you upgrade React.

- [#3107](https://github.com/FormidableLabs/victory/pull/3107) [`4c436bd`](https://github.com/FormidableLabs/victory/commit/4c436bd47b835e795e96bc205cdf9c590fe92ddb) - Remove the UMD bundles (`dist/<package>.js` and `dist/<package>.min.js`). To use Victory in the browser without a build step, import it as ESM from a CDN with an import map; see [Using Victory in the browser](https://commerce.nearform.com/open-source/victory/docs/introduction/browser).

- [#3108](https://github.com/FormidableLabs/victory/pull/3108) [`8f16467`](https://github.com/FormidableLabs/victory/commit/8f1646767d6059d764541118284cf71cc1da5c95) - Packages are now built with tsdown and published from `dist/`, with an `exports` map:
  
  - ESM is `dist/*.mjs` and CommonJS is `dist/*.cjs`, with matching `.d.mts`/`.d.cts` types. `main`, `module` and `types` still point at them for older tooling.
  - Only the package root (and `package.json`) can be imported. Deep imports into `lib/`, `es/` or `src/` no longer resolve; import from the package root instead (for example `import { Helpers } from "victory-core"`).
  - The output targets ES2022 and is no longer down-leveled further. If you support older browsers, transpile `node_modules` in your bundler.
  - `src/` is no longer published.

Give your AI agent these facts

Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.

claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp

Add to Cursor Add to VS Code ★ Star on GitHub

Any other MCP client

{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }

Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests

Frequently asked questions

What are the breaking changes when upgrading victory-pie from 37 to 38?

Between victory-pie 37.4.1 and 38.0.0, Vigia found 0 removed exports, 1 changed signatures and 0 removed or changed class or interface members.

What became deprecated in victory-pie 38?

0 exports or members are newly marked as deprecated in victory-pie 38.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/victory-pie/upgrade?from=37.4.1&to=38.0.0