Packages

@vercel/container

27.0.0 · 18 Nov 2026Apache-2.03.8M / weekRepositoryHomepagenpmAtom feed

Upgrading @vercel/container From 0.0.0 to 0.2.0

8 releases in betweenevery note read

Other targets from 0.0.0Latest27.0.0
0
changes to make
0
advisories fixed
4
new
7
fixes

Release by release

  1. 0.2.0

    12 Aug 20261 new
    • New

      Expose the resolved rewrite destination as the request path observed by containers, and warn affected container projects about the behavior change.

  2. 0.1.1

    3 Aug 20261 fix
    • Fixed

      Bump all workspace packages to trigger a full publish from vercel-internal.

  3. 0.1.0

    24 Jul 20261 new
    • New

      Add package manifest to container builder.

  4. 0.0.5

    9 Jul 20261 fix
    • Fixed

      Apply functions configuration (memory, maxDuration, architecture, regions, functionFailoverRegions, experimentalTriggers, supportsCancellation) to container runtime outputs. The @vercel/container builder now resolves matching vercel.json / per-service functions entries at build time, and the CLI writes those settings into the container .vc-config.json.

  5. 0.0.4

    29 Jun 20261 fix
    • Fixed

      Fixed vercel dev for the container framework when used as a top-level build (outside of services).

  6. 0.0.3

    26 Jun 20261 fix
    • Fixed

      Refine container detection for services / experimentalServicesV2.

  7. 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.

  8. 0.0.1

    24 Jun 20261 new · 2 fixes
    • New

      Add an experimental container service runtime. A service with runtime: "container" either builds its Dockerfile/Containerfile and pushes the resulting OCI image to the Vercel Container Registry (VCR), or passes a prebuilt image reference through as build output.

    • Fixed

      vc dev no longer leaks host/shell-only environment variables into container services. Variables that describe the developer's machine rather than the Linux container — notably macOS TMPDIR (/var/folders/.../T), plus HOME, PATH, SHELL, and similar — are now filtered out of the container's env. Previously they were passed through and broke apps that write to the OS temp dir (e.g. Ghost's multer upload middleware failed with EACCES). The container's own values for these are used instead.

    • Fixed

      vc dev now publishes container services on the host port the services orchestrator pre-allocated (meta.port) instead of a Docker-chosen ephemeral port. Service bindings target the pre-allocated port (http://127.0.0.1:<port>/), so a container published on a different port was unreachable for cross-service requests. Falls back to an ephemeral port when no port is provided.

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.