@vercel/fs-detectors
7.12.4 · 18 Nov 2026Apache-2.0508.5k / weekRepositoryHomepagenpmAtom feed
319 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
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
7.11.0
23 Oct 2026Resolve the proxy entrypoint and root-level middleware in one place.
Report the runtime preset for services without a framework.
Minor Changes
Resolve the proxy entrypoint and root-level middleware in one place.
Patch Changes
Report the runtime preset for services without a framework.
7.10.2
22 Oct 2026Only updates a dependency:@vercel/build-utils 15.0.1
7.10.1
22 Oct 2026Load
@vercel/python-analysisonly when checking a Python entrypoint, not when the package loads.
Patch Changes
Load
@vercel/python-analysisonly when checking a Python entrypoint, not when the package loads.
7.10.0
20 Oct 2026Report proxy runtime mismatch before framework conflict.
Minor Changes
Report proxy runtime mismatch before framework conflict.
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.9.1219 Oct 2026@vercel/python-analysis 0.15.1
- 7.9.1016 Oct 2026@vercel/build-utils 14.21.3
- 7.9.915 Oct 2026@vercel/build-utils 14.21.2
- 7.9.814 Oct 2026@vercel/python-analysis 0.15.0@vercel/build-utils 14.21.1
7.9.7
13 Oct 2026Add
detectDaemons, which reads the daemons (name and entrypoint) invercel.jsonorvercel.toml.Accept Dockerfile and Containerfile names anywhere in the basename of explicit service and daemon entrypoints, such as
worker_Dockerfile.
Patch Changes
Add
detectDaemons, which reads the daemons (name and entrypoint) invercel.jsonorvercel.toml.Accept Dockerfile and Containerfile names anywhere in the basename of explicit service and daemon entrypoints, such as
worker_Dockerfile.
7.9.6
9 Oct 2026Accept suffixed Dockerfile and Containerfile names in explicit service and daemon entrypoints.
Patch Changes
Accept suffixed Dockerfile and Containerfile names in explicit service and daemon entrypoints.
7.9.4 – 7.9.52 releases that only update dependencies@vercel/build-utils 14.20.0Show each
- 7.9.58 Oct 2026@vercel/build-utils 14.20.0
- 7.9.46 Oct 2026@vercel/build-utils 14.19.0
7.9.3
5 Oct 2026Add an experimental workspace-scoped install path for Node builds to avoid installing unrelated monorepo workspaces.
Patch Changes
Add an experimental workspace-scoped install path for Node builds to avoid installing unrelated monorepo workspaces.
7.9.1 – 7.9.22 releases that only update dependencies@vercel/build-utils 14.17.0Show each
- 7.9.22 Oct 2026@vercel/build-utils 14.17.0
- 7.9.12 Oct 2026@vercel/build-utils 14.16.0
7.9.0
2 Oct 2026Build 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 ago.modat their root, includingpackage mainand directory service entrypoints.api/**/*.gofunctions and Go handler entrypoints keep using@vercel/go.The build image is
golang:<version>-bookworm, selected from the newer of the go.modtoolchainandgodirectives. The buildpack defaults toGOTOOLCHAIN=local, so the image's Go builds the module. It compiles the package a service entrypoint names, or else the one@vercel/gowould build, passed asVERCEL_GO_TARGET, and the binary runs on distroless Debian 12.Build Rust HTTP servers with a root
Cargo.tomlusing the container builder whenVERCEL_EXPERIMENTAL_BUILDPACK_RUST=1, selecting the build image fromrust-toolchainorrust-toolchain.tomland servingpublic/from the root path. API functions and services with explicit file entrypoints continue using@vercel/rust.vercel devruns schedules that target anentrypoint. It plans them into the same functionsvercel builddoes, 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 invercel dev.
Minor Changes
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 ago.modat their root, includingpackage mainand directory service entrypoints.api/**/*.gofunctions and Go handler entrypoints keep using@vercel/go.The build image is
golang:<version>-bookworm, selected from the newer of the go.modtoolchainandgodirectives. The buildpack defaults toGOTOOLCHAIN=local, so the image's Go builds the module. It compiles the package a service entrypoint names, or else the one@vercel/gowould build, passed asVERCEL_GO_TARGET, and the binary runs on distroless Debian 12.Build Rust HTTP servers with a root
Cargo.tomlusing the container builder whenVERCEL_EXPERIMENTAL_BUILDPACK_RUST=1, selecting the build image fromrust-toolchainorrust-toolchain.tomland servingpublic/from the root path. API functions and services with explicit file entrypoints continue using@vercel/rust.
Patch Changes
vercel devruns schedules that target anentrypoint. It plans them into the same functionsvercel builddoes, 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 invercel dev.
7.8.1
30 Sep 2026Only updates a dependency:@vercel/build-utils 14.14.0
7.8.0
29 Sep 2026Detect Dockerfile and Containerfile projects with the Container framework preset while keeping plain filenames lower priority than other framework matches.
Minor Changes
Detect Dockerfile and Containerfile projects with the Container framework preset while keeping plain filenames lower priority than other framework matches.
7.7.3
26 Sep 2026Build Python schedule entrypoints. A
.pyentrypoint such asjobs/nightly.pyruns as a script once per firing in a private function under_vercel/schedules/. Entrypoints with the samefunctionsconfig 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 withoutfunctionsconfig share_vercel/schedules/default; the others' function is named after thefunctionspatterns 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
.pyfiles from its root, through the zero-config static fallback oroutputDirectory: ".",vercel buildnow warns and lists them.Add
findMatchingFunctionto@vercel/build-utils, which returns thefunctionsentry that applies to a function.
Patch Changes
Build Python schedule entrypoints. A
.pyentrypoint such asjobs/nightly.pyruns as a script once per firing in a private function under_vercel/schedules/. Entrypoints with the samefunctionsconfig 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 withoutfunctionsconfig share_vercel/schedules/default; the others' function is named after thefunctionspatterns 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
.pyfiles from its root, through the zero-config static fallback oroutputDirectory: ".",vercel buildnow warns and lists them.Add
findMatchingFunctionto@vercel/build-utils, which returns thefunctionsentry that applies to a function.
7.7.1 – 7.7.22 releases that only update dependencies@vercel/build-utils 14.13.0Show each
- 7.7.225 Sep 2026@vercel/build-utils 14.13.0
- 7.7.124 Sep 2026@vercel/build-utils 14.12.0
7.7.0
23 Sep 2026Accept 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.
Minor Changes
Accept Python module:attr proxy entrypoints.
Patch Changes
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.
7.6.2
22 Sep 2026Bundle internal runtime helpers into the published package.
7.6.1
22 Sep 2026Only updates a dependency:@vercel/build-utils 14.10.2
7.6.0
21 Sep 2026Re-add @vercel-internals/runtimes as a dev dep to fs-detectors.
7.5.0
18 Sep 2026Add a migration assistant for
experimentalServiceswhich converts a legacyexperimentalServicesconfig intoserviceswith top-level service rewrites. Available undervercel dev,vercel linkandvercel deploy.
7.4.0
17 Sep 2026Reject proxy entrypoints with mismatched runtime.
7.3.0
15 Sep 2026Route 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 aGemfilesits at the build root and no fileentrypointnarrows the build; services with an explicit.rb/.ruentrypoint keep building with@vercel/ruby.vercel devreports that Ruby projects and services are not supported yet.
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
7.2.2
8 Sep 2026Raise the client-side
maxDurationvalidation limit to 3600 seconds.
Patch Changes
Raise the client-side
maxDurationvalidation limit to 3600 seconds.
7.2.1
4 Sep 2026Only updates a dependency:@vercel/build-utils 14.9.1
7.2.0
2 Sep 2026Restored service topology detection (
detectServicesand related types) on the public@vercel/fs-detectorsAPI.
7.1.5 – 7.1.73 releases that only update dependencies@vercel/frameworks 3.34.0@vercel/build-utils 14.9.0Show each
- 7.1.71 Sep 2026@vercel/frameworks 3.34.0@vercel/build-utils 14.9.0
- 7.1.61 Sep 2026@vercel/build-utils 14.8.0
- 7.1.529 Aug 2026@vercel/build-utils 14.7.0
7.1.4
27 Aug 2026Run 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.
Patch Changes
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.
7.1.1 – 7.1.22 releases that only update dependencies@vercel/build-utils 14.5.1Show each
- 7.1.226 Aug 2026@vercel/build-utils 14.5.1
- 7.1.126 Aug 2026@vercel/build-utils 14.5.0
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.