vercel@54.18.3
📦 vercel-cliView on GitHub →
✨ 2 features🐛 6 fixes🔧 3 symbols
Summary
This patch primarily fixes several issues related to running container builds in `vercel dev` mode, improving Docker daemon error reporting, and reusing the container dev server across requests. Dependencies were also updated.
✨ New Features
- The dev server now reuses the container dev server across requests, keeping a live container running for the same service instead of rebuilding the image on every HTTP request.
- Container dev server now correctly discovers `Dockerfile.vercel` / `Containerfile.vercel` opt-in markers when the entrypoint is the `<detect>` sentinel.
🐛 Bug Fixes
- Fixed `vercel dev` for the `container` framework when used as a top-level build (outside of `services`), ensuring the build is recognized by mapping the `<detect>` sentinel to standard Dockerfile names.
- Prevented `@vercel/container build()` from throwing `` `vercel dev` cannot build container images from a Dockerfile `` during dev by ensuring containers are built locally and returned as a stable local tag.
- Fixed an issue where a container build output was incorrectly treated as a zip-based function, preventing the `output.createZip is not a function` error.
- Improved error handling for `vercel dev` when the Docker daemon is not running, providing a clear message instead of a cryptic exit code 125 error.
- Container start failures during dev now correctly name the container and include the underlying Docker error output.
- Aligned `services` and `experimentalServicesV2` service-name validation with the platform schema.