@vercel/container
27.0.0 · 18 Nov 2026Apache-2.03.8M / weekRepositoryHomepagenpmAtom feed
In short
2 new1 internal
Release note
The section about @vercel/container of a note shared by several packages.
Minor Changes
Build standalone Go servers with the Vercel Go buildpack and the container
runtime whenVERCEL_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.
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.