Packages

@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

Other targets from 0.0.1Newest 0.x0.2.0Latest27.0.0
  1. 0.0.1yours
  2. 0.0.2target
0
changes to make
0
advisories fixed
1
new
1
fix

Release by release

  1. 0.0.2

    24 Jun 20261 new · 1 fix
    • New

      Support deploying any project as a container via a Dockerfile.vercel or Containerfile.vercel marker. A new experimental container framework 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 behind VERCEL_USE_EXPERIMENTAL_FRAMEWORKS. The @vercel/container builder now recognizes the .vercel markers, 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 index path inside the nested services/<name>/ output along with a catch-all route, instead of namespacing under _svc/<name>/index with no route to it. Previously a request to the service root never matched the function.

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.