GitHub - creact-labs/creact: Use JSX to automate durable workflows

Use JSX to automate durable workflows . Contribute to creact-labs/creact development by creating an account on GitHub.

Summary

CReact is a TypeScript library for authoring durable workflows and applications using JSX. The runtime reconciles declared state with actual state, tracks dependencies between steps, manages lifecycle, and persists progress across restarts. It is distributed under the Apache-2.0 license as the npm package @creact-labs/creact.

What it is useful for

The project's topic tags and repository description position CReact around durable workflows, jobs, agents, and infrastructure-style automation. Because the runtime persists state across restarts, it fits long-running or crash-tolerant pipelines where resuming mid-execution is important, such as scheduled jobs, background agents, and orchestrated multi-step processes. The dag and dependency-graph tags indicate the runtime orders work by tracking relationships between declared nodes, so engineers describe what should exist and let the runtime handle the rest. The repository description also frames CReact as a way to sync with external state, so jobs and infrastructure definitions can be reconciled against the real-world state of the systems they manage, alongside building reactive apps and agentic programs declared in JSX.

How engineers can use it

The README is short on concrete steps and points at the full documentation site (creact-labs.github.io/creact) and the in-repo docs/ folder for the actual getting-started guide. Based on the documented metadata, the npm package @creact-labs/creact is published, and a reasonable first step is:

npm install @creact-labs/creact

Engineers then author JSX describing the workflows, jobs, agents, or resources they want, and the CReact runtime is responsible for dependency ordering, lifecycle management, and state persistence. Community support lives in GitHub Discussions, and contributions follow the in-tree contribution guidelines.

A limitation worth flagging: the README itself does not include the actual setup or runtime bootstrap steps. Details like compiler configuration, persistence backend, or runtime entry points are not described in the source provided here, so engineers should consult the linked documentation before wiring CReact into a real codebase.