Packages

@vercel/container

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

Upgrading @vercel/container From 0.0.0 to 0.0.1

1 release in betweenevery note read

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

Release by release

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