Packages

@visx/visx

4.0.0 · 11 Jun 2026MIT163.4k / weekRepositoryHomepagenpmAtom feed

Upgrading @visx/visx From 3.8.0 to 4.0.0

9 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 3.8.0Newest 3.x3.12.0
  1. 3.8.0yours
  2. 8 releases
  3. 4.0.0target

Before you upgrade

Tick each one off as you go
  • Breaking4.0.0
  • Breaking4.0.0
  • Breaking4.0.0
  • Breaking4.0.0
  • Breaking4.0.0
  • Breaking4.0.0
  • Breaking4.0.0
  • Breaking4.0.0

Release by release

  1. 4.0.0

    Migration needed11 Jun 20267 new · 18 fixes
    • Breaking

      Upgrade d3-shape, d3-path to 3 #1960

    • Breaking

      React 19 Support #1968

    • Breaking

      Require React 18 or 19 #2009

    • Breaking

      Toolchain updates. Node 18, TypeScript 5, Next 13 #1938

  2. 3.12.0

    7 Nov 20241 new · 1 fix
    • New

      sankey: Add @visx/sankey #1880

    • Fixed

      Fix small error in the code example in the "Theming" section #1863

  3. 3.11.0

    29 May 20241 new
    • New

      xychart: Improve performance when hovering with tooltip #1842

  4. 3.10.4

    24 May 20241 fix
    • Fixed

      brush: Fix brush jumping around after mouseup #1836

  5. 3.10.3

    20 May 20241 fix
    • Fixed

      Fix LegendThreshold #1831

  6. 3.10.2

    9 Mar 20241 fix
    • Fixed

      Explicit type exports in @visx/responsive #1809

  7. 3.10.1nothing new or fixed in the note

  8. 3.10.0

    8 Mar 20241 fix
    • Fixed

      Improve typing in @visx/responsive enhancers #1783

25 other lines we could not sort, mostly version bumps
  • Upgrade babel #1891

    4.0.0
  • Update actions/cache from v1 to v4.3.0 #1926

    4.0.0
  • Migrate to vitest #1935

    4.0.0
  • demo: Rm deps and update styles #1940

    4.0.0
  • Remove jest #1945

    4.0.0
  • Node 20 #1946

    4.0.0
  • Migrate to jsdom #1947

    4.0.0
  • Upgrade to vitest 3 #1949

    4.0.0
  • Node 22 #1950

    4.0.0
  • Upgrade to vitest 4 #1951

    4.0.0

39 internal lines (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.