Skip to content
← DocumentationDownload raw source

LANGUAGE V1 · FROZEN REFERENCE

Capability registry

274 results · Page 11 of 23

react

react router

unsupported — Laygent v1 does not implement react router in its react target.

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

redux

unsupported — Laygent v1 does not implement redux in its react target.

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

remix

unsupported — Laygent v1 does not implement remix in its react target.

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

reusable components

partial — Parameterized components expand during compilation and are not retained as reusable React components.

Requirements and limitations
Id
react.reusable_components
Status
partial
Aliases
  • reusable components
  • react reusable components
  • use reusable components
  • add reusable components
  • support reusable components
Evidence
Limitation
Parameterized components expand during compilation and are not retained as reusable React components.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
react

server actions

unsupported — Laygent v1 does not implement server actions in its react target.

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

server components

unsupported — Laygent v1 does not implement server components in its react target.

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

state architecture

partial — State is handled by the generated DOM runtime rather than idiomatic React hooks.

Requirements and limitations
Id
react.state_architecture
Status
partial
Aliases
  • react hooks
  • useState
  • react state
  • component state
  • state architecture
  • react state architecture
  • use state architecture
  • add state architecture
  • support state architecture
Evidence
Limitation
State is handled by the generated DOM runtime rather than idiomatic React hooks.
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
react

suspense boundaries

unsupported — Laygent v1 does not implement suspense boundaries in its react target.

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

tsx pages

supported — Laygent v1 implements tsx pages in its react target.

Requirements and limitations
Id
react.tsx_pages
Status
supported
Aliases
  • tsx pages
  • react tsx pages
  • use tsx pages
  • add tsx pages
  • support tsx pages
Evidence
react_export.py Vite React exporter
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
react

vite export

supported — Laygent v1 implements vite export in its react target.

Requirements and limitations
Id
react.vite_export
Status
supported
Aliases
  • react app
  • typescript react
  • vite project
  • react export
  • vite export
  • react vite export
  • use vite export
  • add vite export
  • support vite export
Evidence
react_export.py Vite React exporter
Limitation
Required slots
None
Dependencies
None
Conflicts
None
Defaults
Clarify when
None
Alternatives
None
react

zustand

unsupported — Laygent v1 does not implement zustand in its react target.

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

browser runtime

supported — Laygent v1 implements browser runtime in its typescript target.

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