Packages

@vercel/build-utils

15.5.0 · 18 Nov 2026Apache-2.07.9M / weekRepositoryHomepagenpmAtom feed

Your version

14.23.0

20 Oct 2026Where it was published

In short

1 deprecated1 new2 fixed

  • Deprecated

    schedules in vercel.json can now be an object keyed by schedule name, like "schedules": { "nightly": { "schedule": "0 0 * * *", "path": "/api/cron" } }. vercel build writes schedules to Build Output config.json in the format it was given, and builders can return it from getDevManifest. The array of named schedules still works but is deprecated, and vercel build and vercel dev warn when it's used.

Release note

The section about @vercel/build-utils of a note shared by several packages.

Minor Changes

  • Require name for schedules entries in vercel.json and Build Output config.json. Schedules without a name no longer get a derived default name, and getScheduleName and defaultScheduleName are removed from @vercel/build-utils.

  • Deprecated

    schedules in vercel.json can now be an object keyed by schedule name, like "schedules": { "nightly": { "schedule": "0 0 * * *", "path": "/api/cron" } }. vercel build writes schedules to Build Output config.json in the format it was given, and builders can return it from getDevManifest. The array of named schedules still works but is deprecated, and vercel build and vercel dev warn when it's used.

Patch Changes

  • Accept service bindings on daemons in vercel.json.

  • Fix ENOENT build failures when daemons are deployed alongside a zero-config server app that has no public/ directory.

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.