Packages

@vercel/fs-detectors

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

Your version

319 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.

  1. 7.11.1 – 7.12.410 releases with no change for you1 dependency update, 9 without a note@vercel/build-utils 15.1.0Show each
  2. 7.11.0

    23 Oct 2026
    • Resolve the proxy entrypoint and root-level middleware in one place.

    • Report the runtime preset for services without a framework.

  3. 7.10.2

    22 Oct 2026

    Only updates a dependency:@vercel/build-utils 15.0.1

  4. 7.10.1

    22 Oct 2026
  5. 7.10.0

    20 Oct 2026
    • Report proxy runtime mismatch before framework conflict.

  6. 7.9.8 – 7.9.124 releases that only update dependencies@vercel/python-analysis 0.15.1@vercel/build-utils 14.21.3Show each
  7. 7.9.7

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

    • 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 2026
    • Accept suffixed Dockerfile and Containerfile names in explicit service and daemon entrypoints.

  9. 7.9.4 – 7.9.52 releases that only update dependencies@vercel/build-utils 14.20.0Show each
  10. 7.9.3

    5 Oct 2026
    • Add an experimental workspace-scoped install path for Node builds to avoid installing unrelated monorepo workspaces.

  11. 7.9.1 – 7.9.22 releases that only update dependencies@vercel/build-utils 14.17.0Show each
  12. 7.9.0

    2 Oct 2026
    • Build standalone Go servers with the Vercel Go buildpack and the container runtime when VERCEL_EXPERIMENTAL_BUILDPACK_GO=1, instead of running them behind the IPC proxy on Lambda. This applies to zero-config Go projects and Go services with a go.mod at their root, including package main and directory service entrypoints. api/**/*.go functions and Go handler entrypoints keep using @vercel/go.

      The build image is golang:<version>-bookworm, selected from the newer of the go.mod toolchain and go directives. The buildpack defaults to GOTOOLCHAIN=local, so the image's Go builds the module. It compiles the package a service entrypoint names, or else the one @vercel/go would build, passed as VERCEL_GO_TARGET, and the binary runs on distroless Debian 12.

    • Build Rust HTTP servers with a root Cargo.toml using the container builder when VERCEL_EXPERIMENTAL_BUILDPACK_RUST=1, selecting the build image from rust-toolchain or rust-toolchain.toml and serving public/ from the root path. API functions and services with explicit file entrypoints continue using @vercel/rust.

    • vercel dev runs schedules that target an entrypoint. It plans them into the same functions vercel build does, such as _vercel/schedules/default, registers each one with the local scheduler, and builds it with the entrypoint's builder. Schedule functions are only invoked by the scheduler, never by a public URL. Projects with services still reject schedule entrypoints in vercel dev.

  13. 7.8.1

    30 Sep 2026

    Only updates a dependency:@vercel/build-utils 14.14.0

  14. 7.8.0

    29 Sep 2026
    • Detect Dockerfile and Containerfile projects with the Container framework preset while keeping plain filenames lower priority than other framework matches.

  15. 7.7.3

    26 Sep 2026
    • Build Python schedule entrypoints. A .py entrypoint such as jobs/nightly.py runs as a script once per firing in a private function under _vercel/schedules/. Entrypoints with the same functions config share one function, which runs the script for the dispatched schedule name, so the project's dependencies are bundled once per distinct config instead of once per script. Entrypoints without functions config share _vercel/schedules/default; the others' function is named after the functions patterns their config came from, such as _vercel/schedules/jobs/report. Schedule names must be unique within a shared function.

      Declared schedule entrypoints are not served as static files, but other files follow the normal static rules. When a project with Python schedule entrypoints publishes other .py files from its root, through the zero-config static fallback or outputDirectory: ".", vercel build now warns and lists them.

      Add findMatchingFunction to @vercel/build-utils, which returns the functions entry that applies to a function.

  16. 7.7.1 – 7.7.22 releases that only update dependencies@vercel/build-utils 14.13.0Show each
  17. 7.7.0

    23 Sep 2026
    • Accept Python module:attr proxy entrypoints.

    • Use Ruby buildpacks for services with an explicit root config.ru entrypoint when buildpacks are enabled and a Gemfile exists at the service root. Preserve the Ruby runtime for function handlers and custom Rack entrypoints.

    • Accept runtime-specific schedule entrypoints and provide build plumbing for lowering dedicated entrypoints to function targets. All schedule entrypoints must use one runtime, including for static frameworks and framework: null. Entrypoints must also match the runtime of frameworks that own one (Next.js, FastAPI, Express). The builder contract still supports multiple entrypoints per function for future runtimes.

  18. 7.6.2

    22 Sep 2026
    • Bundle internal runtime helpers into the published package.

  19. 7.6.1

    22 Sep 2026

    Only updates a dependency:@vercel/build-utils 14.10.2

  20. 7.6.0

    21 Sep 2026
    • Re-add @vercel-internals/runtimes as a dev dep to fs-detectors.

  21. 7.5.0

    18 Sep 2026
    • Add a migration assistant for experimentalServices which converts a legacy experimentalServices config into services with top-level service rewrites. Available under vercel dev, vercel link and vercel deploy.

  22. 7.4.0

    17 Sep 2026
    • Reject proxy entrypoints with mismatched runtime.

  23. 7.3.0

    15 Sep 2026
    • Route Ruby services and zero-config Ruby projects (Rails and Rack) to the experimental Ruby buildpack container builder behind VERCEL_EXPERIMENTAL_BUILDPACK_RUBY=1. The buildpack is selected only when a Gemfile sits at the build root and no file entrypoint narrows the build; services with an explicit .rb/.ru entrypoint keep building with @vercel/ruby. vercel dev reports that Ruby projects and services are not supported yet.

  24. 7.2.3 – 7.2.53 releases that only update dependencies@vercel/build-utils 14.10.1@vercel/routing-utils 6.6.0@vercel/frameworks 3.34.0Show each
  25. 7.2.2

    8 Sep 2026
    • Raise the client-side maxDuration validation limit to 3600 seconds.

  26. 7.2.1

    4 Sep 2026

    Only updates a dependency:@vercel/build-utils 14.9.1

  27. 7.2.0

    2 Sep 2026
    • Restored service topology detection (detectServices and related types) on the public @vercel/fs-detectors API.

  28. 7.1.5 – 7.1.73 releases that only update dependencies@vercel/frameworks 3.34.0@vercel/build-utils 14.9.0Show each
  29. 7.1.4

    27 Aug 2026
    • Run on-disk JavaScript workers with a lazily resolved system Node.js executable in native CLI installations, and install the matching Build Utils preview tarball for dynamically installed Builders.

  30. 7.1.1 – 7.1.22 releases that only update dependencies@vercel/build-utils 14.5.1Show each

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.