Skip to content
← DocumentationDownload raw source

LANGUAGE V1 · FROZEN REFERENCE

Capability registry

274 results · Page 19 of 23

supabase

webhook forward

supported — Laygent v1 implements webhook forward in its supabase target.

Requirements and limitations
Id
supabase.webhook_forward
Status
supported
Aliases
  • outgoing webhook
  • forward to api
  • secret endpoint
  • notify url
  • webhook forward
  • supabase webhook forward
  • use webhook forward
  • add webhook forward
  • support webhook forward
Evidence
fullstack.py backend parser/generator and publishing.py provisioning
Limitation
Required slots
  • secret_name
Dependencies
  • supabase.edge_functions
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
vercel

analytics

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

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

arbitrary functions

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

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

blob

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

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

build settings

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

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

cron

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

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

custom domains

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

Requirements and limitations
Id
vercel.custom_domains
Status
unsupported
Aliases
  • custom domains
  • vercel custom domains
  • use custom domains
  • add custom domains
  • support custom domains
Evidence
Limitation
Laygent v1 does not implement custom domains in its vercel target.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
  • manual domain configuration after deployment
vercel

deployment status

partial — The initial deployment state and URL are returned, but ongoing monitoring and management are absent.

Requirements and limitations
Id
vercel.deployment_status
Status
partial
Aliases
  • deployment status
  • vercel deployment status
  • use deployment status
  • add deployment status
  • support deployment status
Evidence
Limitation
The initial deployment state and URL are returned, but ongoing monitoring and management are absent.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
vercel

dns management

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

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

domain purchase

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

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

edge config

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

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

edge middleware

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

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