@vercel/container
27.0.0 · 18 Nov 2026Apache-2.03.8M / weekRepositoryHomepagenpmAtom feed
Upgrading @vercel/container From 0.0.1 to 0.0.2
1 release in betweenevery note read
Release by release
- New
Support deploying any project as a container via a
Dockerfile.vercelorContainerfile.vercelmarker. A new experimentalcontainerframework preset detects these files and is listed first so it takes precedence over all other frameworks — a project that also looks like (e.g.) a Next.js app will deploy as a container when one of these markers is present. As an experimental framework it is gated behindVERCEL_USE_EXPERIMENTAL_FRAMEWORKS. The@vercel/containerbuilder now recognizes the.vercelmarkers, auto-discovers them when its entrypoint is<detect>, and supports root (non-service) container deploys. - Fixed
Fix container service build output so requests reach the function. Container services now do a normal build, emitting the function at the natural
indexpath inside the nestedservices/<name>/output along with a catch-all route, instead of namespacing under_svc/<name>/indexwith no route to it. Previously a request to the service root never matched the function.
- New
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.