Packages

@vercel/fs-detectors

7.12.4 · 18 Nov 2026Apache-2.0508.5k / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/fs-detectors From 6.15.3 to 7.12.4

58 releases in betweennotes for 44

Other targets from 6.15.3Newest 6.x6.15.10
  1. 6.15.3yours
  2. 6 releases
  3. 7.0.0major
  4. 50 releases
  5. 7.12.4target
  6. 16 pre
2+
changes to make
0
advisories fixed
12+
new
13+
fixes

Counted from 44 of 58 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking7.0.0
  • Breaking7.0.0

Release by release

  1. 7.11.1 – 7.12.410 releases, nothing new or fixed; 9 without a note

  2. 7.11.0

    23 Oct 20262 fixes
    • Fixed

      Resolve the proxy entrypoint and root-level middleware in one place.

    • Fixed

      Report the runtime preset for services without a framework.

  3. 7.10.2nothing new or fixed in the note

  4. 7.10.1

    22 Oct 20261 fix
  5. 7.10.0

    20 Oct 20261 new
    • New

      Report proxy runtime mismatch before framework conflict.

  6. 7.9.8 – 7.9.124 releases, nothing new or fixed in the notes

  7. 7.9.7

    13 Oct 20261 new · 1 fix
    • New

      Add detectDaemons, which reads the daemons (name and entrypoint) in vercel.json or vercel.toml.

    • Fixed

      Accept Dockerfile and Containerfile names anywhere in the basename of explicit service and daemon entrypoints, such as worker_Dockerfile.

  8. 7.9.6

    9 Oct 20261 fix
    • Fixed

      Accept suffixed Dockerfile and Containerfile names in explicit service and daemon entrypoints.

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