Skip to content
← DocumentationDownload raw source

LANGUAGE V1 · FROZEN REFERENCE

Capability registry

274 results · Page 21 of 23

vercel

queues

unsupported — Laygent v1 does not implement queues in its vercel target.

Requirements and limitations
Id
vercel.queues
Status
unsupported
Aliases
  • queues
  • vercel queues
  • use queues
  • add queues
  • support queues
Evidence
Limitation
Laygent v1 does not implement queues in its vercel target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
vercel

rollback

unsupported — Laygent v1 does not implement rollback in its vercel target.

Requirements and limitations
Id
vercel.rollback
Status
unsupported
Aliases
  • rollback
  • vercel rollback
  • use rollback
  • add rollback
  • support rollback
Evidence
Limitation
Laygent v1 does not implement rollback in its vercel target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
vercel

speed insights

unsupported — Laygent v1 does not implement speed insights in its vercel target.

Requirements and limitations
Id
vercel.speed_insights
Status
unsupported
Aliases
  • speed insights
  • vercel speed insights
  • use speed insights
  • add speed insights
  • support speed insights
Evidence
Limitation
Laygent v1 does not implement speed insights in its vercel target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
vercel

spend management

unsupported — Laygent v1 does not implement spend management in its vercel target.

Requirements and limitations
Id
vercel.spend_management
Status
unsupported
Aliases
  • spend management
  • vercel spend management
  • use spend management
  • add spend management
  • support spend management
Evidence
Limitation
Laygent v1 does not implement spend management in its vercel target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
vercel

static output configuration

supported — Laygent v1 implements static output configuration in its vercel target.

Requirements and limitations
Id
vercel.static_output_configuration
Status
supported
Aliases
  • static output configuration
  • vercel static output configuration
  • use static output configuration
  • add static output configuration
  • support static output configuration
Evidence
integrations.py OAuth and publishing.py Vercel project/deployment flow
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
vercel

team selection

supported — Laygent v1 implements team selection in its vercel target.

Requirements and limitations
Id
vercel.team_selection
Status
supported
Aliases
  • team selection
  • vercel team selection
  • use team selection
  • add team selection
  • support team selection
Evidence
integrations.py OAuth and publishing.py Vercel project/deployment flow
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
vercel

vite configuration

supported — Laygent v1 implements vite configuration in its vercel target.

Requirements and limitations
Id
vercel.vite_configuration
Status
supported
Aliases
  • vite configuration
  • vercel vite configuration
  • use vite configuration
  • add vite configuration
  • support vite configuration
Evidence
integrations.py OAuth and publishing.py Vercel project/deployment flow
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
vercel

workflows

unsupported — Laygent v1 does not implement workflows in its vercel target.

Requirements and limitations
Id
vercel.workflows
Status
unsupported
Aliases
  • workflows
  • vercel workflows
  • use workflows
  • add workflows
  • support workflows
Evidence
Limitation
Laygent v1 does not implement workflows in its vercel target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
git

binary assets

unsupported — Laygent v1 does not implement binary assets in its git target.

Requirements and limitations
Id
git.binary_assets
Status
unsupported
Aliases
  • binary assets
  • git binary assets
  • use binary assets
  • add binary assets
  • support binary assets
Evidence
Limitation
Laygent v1 does not implement binary assets in its git target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
git

branch creation

partial — The publish flow writes the default branch; user-directed branch workflows are absent.

Requirements and limitations
Id
git.branch_creation
Status
partial
Aliases
  • branch creation
  • git branch creation
  • use branch creation
  • add branch creation
  • support branch creation
Evidence
Limitation
The publish flow writes the default branch; user-directed branch workflows are absent.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
git

cherry pick

unsupported — Laygent v1 does not implement cherry pick in its git target.

Requirements and limitations
Id
git.cherry_pick
Status
unsupported
Aliases
  • cherry pick
  • git cherry pick
  • use cherry pick
  • add cherry pick
  • support cherry pick
Evidence
Limitation
Laygent v1 does not implement cherry pick in its git target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
git

collaborators webhooks

unsupported — Laygent v1 does not implement collaborators webhooks in its git target.

Requirements and limitations
Id
git.collaborators_webhooks
Status
unsupported
Aliases
  • collaborators webhooks
  • git collaborators webhooks
  • use collaborators webhooks
  • add collaborators webhooks
  • support collaborators webhooks
Evidence
Limitation
Laygent v1 does not implement collaborators webhooks in its git target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None