Packages

@fastify/error

4.2.1 · 10 Oct 2026MIT23.5M / weekRepositoryHomepagenpmAtom feed

Upgrading @fastify/error From 3.1.0 to 4.2.1

9 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 3.1.0Newest 3.x3.4.1
The note of 4.0.0 lists no breaking change or deprecation, which is rare for a major.
  1. 3.1.0yours
  2. 5 releases
  3. 4.0.0major
  4. 2 releases
  5. 4.2.1target
?
changes to make
0
advisories fixed
6
new
5
fixes

Release by release

  1. 4.2.1nothing new or fixed in the note

  2. 4.2.0

    1 Jun 20251 new
    • New

      Implement instanceof

  3. 4.1.0

    12 Mar 20251 new · 2 fixes
    • New

      Add captureStackTrace parameter

    • Fixed

      Migrate from tap to node test and c8

    • Fixed

      c8 100 percent code coverage

  4. 4.0.0nothing new or fixed in the note

  5. 3.4.1

    4 Nov 20231 fix
    • Fixed

      Cause last element index check

  6. 3.4.0

    3 Oct 20232 new · 1 fix
    • New

      Use node: prefix to bypass require.cache call for builtins

    • New

      Added support for cause

    • Fixed

      Fix type of base argument create error

  7. 3.3.0

    23 Jun 20231 fix
    • Fixed

      Fix type of Base argument to createError

  8. 3.2.1

    3 Jun 20232 new
    • New

      Add benchmarks, improve performance of stackTraceLimit === 0

    • New

      Use spread operator

5 other lines we could not sort, mostly version bumps
  • Merge next into master

    4.0.0
  • Revert "Fix type of Base argument to createError"

    3.3.0
  • Improve perf of error creation

    3.3.0
  • types: Check error argument type

    3.2.1
  • Strictly type createError

    3.2.0

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