Packages

@vercel/fs-detectors

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

Upgrading @vercel/fs-detectors From 7.8.1 to 7.9.0

1 release in betweenevery note read

Other targets from 7.8.1Newest 7.x, Latest7.12.4
  1. 7.8.1yours
  2. 7.9.0target
0
changes to make
0
advisories fixed
2
new
1
fix

Release by release

  1. 7.9.0

    2 Oct 20262 new · 1 fix
    • New

      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.

    • New

      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.

    • Fixed

      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.

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.