Packages

finalhandler

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

Upgrading finalhandler From 0.3.5 to 2.1.1

23 releases in betweennotes for 12

Other targets from 0.3.5Newest 0.x0.5.1
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.3.5yours
  2. 1 release
  3. 0.4.0major
  4. 1 release
  5. 0.5.0major
  6. 1 release
  7. 1.0.0major
  8. 14 releases
  9. 2.0.0major
  10. 2.1.0breaking
  11. 2.1.1target
1+
change to make
0
advisories fixed
?
new
2+
fixes

Counted from 12 of 23 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. 0.3.6 – 1.1.013 releases, nothing new or fixed; 7 without a note

10 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

  • Change invalid or non-numeric status code to 500

    0.5.0

  • Overwrite status message to match set status code

    0.5.0

  • Prefer err.statusCode if err.status is invalid

    0.5.0

  • Set response headers from err.headers object

    0.5.0

  • Use statuses instead of http module for status messages

    0.5.0

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