Packages

@vercel/routing-utils

6.6.1 · 28 Oct 2026Apache-2.02.3M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/routing-utils From 5.0.0 to 6.6.1

30 releases in betweennotes for 29

Other targets from 5.0.0Newest 5.x5.3.3
  1. 5.0.0yours
  2. 17 releases
  3. 6.0.0major
  4. 11 releases
  5. 6.6.1target
2+
changes to make
0
advisories fixed
20+
new
12+
fixes

Counted from 29 of 30 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking6.0.0
  • Deprecated6.0.0

Release by release

  1. 6.6.1no release note

  2. 6.6.0

    14 Sep 20261 fix
    • Fixed

      Fix route ordering so project middleware always runs before builder-generated routes.

  3. 6.5.0

    13 Aug 20261 new
    • New

      Move middleware matcher utils from node builder to general build utils.

  4. 6.4.1

    3 Aug 20261 fix
    • Fixed

      Bump all workspace packages to trigger a full publish from vercel-internal.

  5. 6.4.0

    25 Jun 20261 new
    • New

      Make hand-written service-targeted route/rewrite destination config less repetitive and verbose by making the type discriminator optional.

  6. 6.3.1

    23 Jun 20261 new
    • New

      Support request.path transforms on routes and high-level rewrites, lowering path-to-regexp parameters such as /:path* to low-level capture references such as /$1 [config] support request path transforms in the router builder [cli] preserve request path transform syntax and environment metadata across AI/manual route edits

  7. 6.3.0

    10 Jun 20261 new
    • New

      Support a service-targeted destination object ({ type: "service", service, path }) on routes and rewrites, so a route/rewrite can delegate into a named service. The service handoff is terminal: continue: true together with a service destination is rejected during normalization.

  8. 6.2.0

    30 Apr 20261 new
    • New

      Upgrade to TypeScript 5.9

1 other line we could not sort, mostly version bumps
  • Revert "[routing-utils] Support Conditions and Mitigate in vercel.json"

    5.0.5

1 internal line (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.