Packages

through2

5.0.12 · 19 Oct 2026MIT57.7M / weekRepositorynpmAtom feed

Upgrading through2 From 0.0.2 to 5.0.12

49 releases in betweennotes for 13

Reading releases, release notes and advisories…

Other targets from 0.0.2Newest 0.x0.6.5
4.0.0, 3.0.0, 2.0.0, 1.0.0 have no release note on GitHub or in the repository's changelog, so their breaking changes are missing from the counts below.
  1. 0.0.2yours
  2. 3 releases
  3. 0.1.0major
  4. 0.2.0major
  5. 3 releases
  6. 0.3.0major
  7. 0.4.0major
  8. 2 releases
  9. 0.5.0major
  10. 1 release
  11. 0.6.0major
  12. 5 releases
  13. 1.0.0major
  14. 3 releases
  15. 2.0.0major
  16. 5 releases
  17. 3.0.0major
  18. 2 releases
  19. 4.0.0major
  20. 2 releases
  21. 5.0.0major
  22. 11 releases
  23. 5.0.12target
1+
change to make
0
advisories fixed
1+
new
1+
fix

Counted from 13 of 49 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking5.0.0

Release by release

  1. 5.0.11 – 5.0.122 releases, nothing new or fixed in the notes

  2. 5.0.10

    29 Jul 20261 fix
    • Fixed

      Fixes for ts@7

  3. 5.0.2 – 5.0.98 releases, nothing new or fixed in the notes

  4. 5.0.1

    15 May 20261 new
    • New

      Add CJS support for Node.js 22.12+

  5. 5.0.0

    Migration needed7 May 2026
    • Breaking

      ESM rewrite, named exports, async + async-generator transforms, /web subpath

  6. 0.0.3 – 4.0.236 releases, no release note

3 other lines we could not sort, mostly version bumps
  • Downgrade broken changelog maker, backfill missing

    5.0.11
  • deps-dev: bump typescript from 6.0.3 to 7.0.2

    5.0.10
  • deps-dev: bump @types/node from 25.9.4 to 26.0.1

    5.0.4

3 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.