Packages

nitropack

2.13.6 · 2 Nov 2026MIT3.9M / weekRepositoryHomepagenpmAtom feed

Upgrading nitropack From 0.4.21 to 0.6.1

10 releases in betweennotes for 2

Reading releases, release notes and advisories…

Other targets from 0.4.21Clears its 2 advisories2.13.4Latest2.13.6
  1. 0.4.21yours
  2. 3 releases
  3. 0.5.0major
  4. 4 releases
  5. 0.6.0major
  6. 0.6.1target
8+
changes to make
0
advisories fixed
19+
new
21+
fixes

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

Before you upgrade

Tick each one off as you go
  • Breaking0.6.0
  • Breaking0.6.0
  • Breaking0.6.0
  • Breaking0.5.0
  • Breaking0.5.0
  • Breaking0.5.0
  • Breaking0.5.0
  • Breaking0.5.0

Security

Release by release

  1. 0.6.1no release note

  2. 0.6.0

    Migration needed18 Oct 202211 new · 16 fixes
    • Breaking

      H3 updated to to 0.8x [Release Notes]

    • Breaking

      Experimental routes is renamed to routeRules

    • Breaking

      ⚠️ Rename routeOptions to routeRules

    • New

      Support redirect, headers, and cors route rules

  3. 0.5.1 – 0.5.44 releases, no release note

  4. 0.5.0

    Migration needed1 Sep 20228 new · 5 fixes
    • Breaking

      ⚠️ Update unenv to 0.6.x

    • Breaking

      externals: ⚠️ Fall back to mlly resolver in more cases

    • Breaking

      ⚠️ NITRO_PRESET should have the highest priority

    • Breaking

      ⚠️ Rename options autoImport to imports

  5. 0.4.22 – 0.4.243 releases, no release note

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