Skip to content
← DocumentationDownload raw source

LANGUAGE V1 · FROZEN REFERENCE

Capability registry

274 results · Page 12 of 23

typescript

custom classes

unsupported — Laygent v1 does not implement custom classes in its typescript target.

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

custom interfaces

unsupported — Laygent v1 does not implement custom interfaces in its typescript target.

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

custom modules

unsupported — Laygent v1 does not implement custom modules in its typescript target.

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

custom types

unsupported — Laygent v1 does not implement custom types in its typescript target.

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

decorators

unsupported — Laygent v1 does not implement decorators in its typescript target.

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

edge function output

supported — Laygent v1 implements edge function output in its typescript target.

Requirements and limitations
Id
typescript.edge_function_output
Status
supported
Aliases
  • edge function output
  • typescript edge function output
  • use edge function output
  • add edge function output
  • support edge function output
Evidence
react_export.py and fullstack.py generated TypeScript
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
typescript

generated types

partial — Generated files contain TypeScript, but Laygent cannot author arbitrary domain types.

Requirements and limitations
Id
typescript.generated_types
Status
partial
Aliases
  • generated types
  • typescript generated types
  • use generated types
  • add generated types
  • support generated types
Evidence
Limitation
Generated files contain TypeScript, but Laygent cannot author arbitrary domain types.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
typescript

generics

unsupported — Laygent v1 does not implement generics in its typescript target.

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

monorepos

unsupported — Laygent v1 does not implement monorepos in its typescript target.

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

path aliases

unsupported — Laygent v1 does not implement path aliases in its typescript target.

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

type check

supported — Laygent v1 implements type check in its typescript target.

Requirements and limitations
Id
typescript.type_check
Status
supported
Aliases
  • type check
  • typescript type check
  • use type check
  • add type check
  • support type check
Evidence
react_export.py and fullstack.py generated TypeScript
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
supabase

admin auth

unsupported — Laygent v1 does not implement admin auth in its supabase target.

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