Packages

finalhandler

2.1.1 · 1 Dec 2025MIT213.8M / weekRepositoryHomepagenpmAtom feed

Upgrading finalhandler From 1.0.0 to 2.1.1

17 releases in betweennotes for 10

Other targets from 1.0.0Newest 1.x1.3.2
2.0.0 has no release note on GitHub or in the repository's changelog, so its breaking changes are missing from the counts below.
  1. 1.0.0yours
  2. 14 releases
  3. 2.0.0major
  4. 2.1.0breaking
  5. 2.1.1target
1+
change to make
0
advisories fixed
?
new
2+
fixes

Counted from 10 of 17 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • breaking2.1.0

Release by release

  1. 2.1.1

    1 Dec 20251 fix
    • fixed

      Update engines reference in the pkg

  2. 2.1.0

    Migration needed5 Mar 2025
    • breaking

      Remove unpipe package and use native unpipe method

  3. 1.1.2 – 2.0.07 releases, nothing new or fixed; 4 without a note

  4. 1.1.1

    6 Mar 20181 fix
    • fixed

      Fix 404 output for bad / missing pathnames

  5. 1.0.1 – 1.1.07 releases, nothing new or fixed; 3 without a note

5 other lines we could not sort, mostly version bumps

  • cleanup: Remove unnecessary devDependency readable-stream

    2.1.0

  • cleanup: Remove unnecessary devDependency safe-buffer

    2.1.0

  • cleanup: Remove setImmediate support check

    2.1.0

  • Remove set content headers that break response

    1.2.0

  • Use res.headersSent when available

    1.1.0

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