@creact-labs/creact 0.1.0

package/LICENSE

@@ -0,0 +1,212 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+   "License" shall mean the terms and conditions for use, reproduction,
+   and distribution as defined by Sections 1 through 9 of this document.
+
+   "Licensor" shall mean the copyright owner or entity authorized by
+   the copyright owner that is granting the License.
+
+   "Legal Entity" shall mean the union of the acting entity and all
+   other entities that control, are controlled by, or are under common
+   control with that entity. For the purposes of this definition,
+   "control" means (i) the power, direct or indirect, to cause the
+   direction or management of such entity, whether by contract or
+   otherwise, or (ii) ownership of fifty percent (50%) or more of the
+   outstanding shares, or (iii) beneficial ownership of such entity.
+
+   "You" (or "Your") shall mean an individual or Legal Entity exercising
+   permissions granted by this License.
+
+   "Source" form shall mean the preferred form for making modifications,
+   including but not limited to software source code, documentation
+   source, and configuration files.
+
+   "Object" form shall mean any form resulting from mechanical
+   transformation or translation of a Source form, including but
+   not limited to compiled object code, generated documentation,
+   and conversions to other media types.
+
+   "Work" shall mean the work of authorship, whether in Source or
+   Object form, made available under the License, as indicated by a
+   copyright notice that is included in or attached to the work
+   (an example is provided in the Appendix below).
+
+   "Derivative Works" shall mean any work, whether in Source or Object
+   form, that is based on (or derived from) the Work and for which the
+   editorial revisions, annotations, elaborations, or other modifications
+   represent, as a whole, an original work of authorship. For the purposes
+   of this License, Derivative Works shall not include works that remain
+   separable from, or merely link (or bind by name) to the interfaces of,
+   the Work and Derivative Works thereof.
+
+   "Contribution" shall mean any work of authorship, including
+   the original version of the Work and any modifications or additions
+   to that Work or Derivative Works thereof, that is intentionally
+   submitted to Licensor for inclusion in the Work by the copyright owner
+   or by an individual or Legal Entity authorized to submit on behalf of
+   the copyright owner. For the purposes of this definition, "submitted"
+   means any form of electronic, verbal, or written communication sent
+   to the Licensor or its representatives, including but not limited to
+   communication on electronic mailing lists, source code control systems,
+   and issue tracking systems that are managed by, or on behalf of, the
+   Licensor for the purpose of discussing and improving the Work, but
+   excluding communication that is conspicuously marked or otherwise
+   designated in writing by the copyright owner as "Not a Contribution."
+
+   "Contributor" shall mean Licensor and any individual or Legal Entity
+   on behalf of whom a Contribution has been received by Licensor and
+   subsequently incorporated within the Work.
+
+2. Grant of Copyright License.
+
+   Subject to the terms and conditions of this License, each Contributor
+   hereby grants to You a perpetual, worldwide, non-exclusive, no-charge,
+   royalty-free, irrevocable copyright license to reproduce, prepare
+   Derivative Works of, publicly display, publicly perform, sublicense,
+   and distribute the Work and such Derivative Works in Source or Object
+   form.
+
+3. Grant of Patent License.
+
+   Subject to the terms and conditions of this License, each Contributor
+   hereby grants to You a perpetual, worldwide, non-exclusive, no-charge,
+   royalty-free, irrevocable (except as stated in this section) patent
+   license to make, have made, use, offer to sell, sell, import, and
+   otherwise transfer the Work, where such license applies only to those
+   patent claims licensable by such Contributor that are necessarily
+   infringed by their Contribution(s) alone or by combination of their
+   Contribution(s) with the Work to which such Contribution(s) was
+   submitted. If You institute patent litigation against any entity
+   (including a cross-claim or counterclaim in a lawsuit) alleging that
+   the Work or a Contribution incorporated within the Work constitutes
+   direct or contributory patent infringement, then any patent licenses
+   granted to You under this License for that Work shall terminate as of
+   the date such litigation is filed.
+
+4. Redistribution.
+
+   You may reproduce and distribute copies of the Work or Derivative
+   Works thereof in any medium, with or without modifications, and in
+   Source or Object form, provided that You meet the following conditions:
+
+   (a) You must give any other recipients of the Work or Derivative Works
+       a copy of this License; and
+
+   (b) You must cause any modified files to carry prominent notices
+       stating that You changed the files; and
+
+   (c) You must retain, in the Source form of any Derivative Works that
+       You distribute, all copyright, patent, trademark, and attribution
+       notices from the Source form of the Work, excluding those notices
+       that do not pertain to any part of the Derivative Works; and
+
+   (d) If the Work includes a "NOTICE" text file as part of its
+       distribution, then any Derivative Works that You distribute must
+       include a readable copy of the attribution notices contained
+       within such NOTICE file, excluding those notices that do not
+       pertain to any part of the Derivative Works, in at least one of
+       the following places: within a NOTICE text file distributed as
+       part of the Derivative Works; within the Source form or
+       documentation, if provided along with the Derivative Works; or,
+       within a display generated by the Derivative Works, if and
+       wherever such third-party notices normally appear. The contents
+       of the NOTICE file are for informational purposes only and do not
+       modify the License. You may add Your own attribution notices
+       within Derivative Works that You distribute, alongside or as an
+       addendum to the NOTICE text from the Work, provided that such
+       additional attribution notices cannot be construed as modifying
+       the License.
+
+   You may add Your own copyright statement to Your modifications and
+   may provide additional or different license terms and conditions
+   for use, reproduction, or distribution of Your modifications, or
+   for any such Derivative Works as a whole, provided Your use,
+   reproduction, and distribution of the Work otherwise complies with
+   the conditions stated in this License.
+
+5. Submission of Contributions.
+
+   Unless You explicitly state otherwise, any Contribution intentionally
+   submitted for inclusion in the Work by You to the Licensor shall be
+   under the terms and conditions of this License, without any additional
+   terms or conditions. Notwithstanding the above, nothing herein shall
+   supersede or modify the terms of any separate license agreement you
+   may have executed with Licensor regarding such Contributions.
+
+6. Trademarks.
+
+   This License does not grant permission to use the trade names,
+   trademarks, service marks, or product names of the Licensor, except
+   as required for reasonable and customary use in describing the
+   origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty.
+
+   Unless required by applicable law or agreed to in writing, Licensor
+   provides the Work (and each Contributor provides its Contributions)
+   on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND,
+   either express or implied, including, without limitation, any
+   warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY,
+   or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for
+   determining the appropriateness of using or redistributing the Work
+   and assume any risks associated with Your exercise of permissions
+   under this License.
+
+8. Limitation of Liability.
+
+   In no event and under no legal theory, whether in tort (including
+   negligence), contract, or otherwise, unless required by applicable
+   law (such as deliberate and grossly negligent acts) or agreed to in
+   writing, shall any Contributor be liable to You for damages,
+   including any direct, indirect, special, incidental, or consequential
+   damages of any character arising as a result of this License or out
+   of the use or inability to use the Work (including but not limited to
+   damages for loss of goodwill, work stoppage, computer failure or
+   malfunction, or any and all other commercial damages or losses), even
+   if such Contributor has been advised of the possibility of such
+   damages.
+
+9. Accepting Warranty or Additional Liability.
+
+   While redistributing the Work or Derivative Works thereof, You may
+   choose to offer, and charge a fee for, acceptance of support, warranty,
+   indemnity, or other liability obligations and/or rights consistent with
+   this License. However, in accepting such obligations, You may act only
+   on Your own behalf and on Your sole responsibility, not on behalf of
+   any other Contributor, and only if You agree to indemnify, defend, and
+   hold each Contributor harmless for any liability incurred by, or
+   claims asserted against, such Contributor by reason of your accepting
+   any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+   To apply the Apache License to your work, attach the following
+   boilerplate notice, with the fields enclosed by brackets "{}"
+   replaced with your own identifying information. (Don't include
+   the brackets!)  The text should be enclosed in the appropriate
+   comment syntax for the file format. We also recommend that a
+   file or class name and description of purpose be included on the
+   same "printed page" as the copyright notice for easier
+   identification within third-party archives.
+
+Copyright 2025 Daniel Coutinho Ribeiro
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/README.md

@@ -0,0 +1,379 @@
+# CReact — React for Infrastructure
+
+Think of it as React's rendering model — but instead of a DOM, you render to the cloud.
+
+Write your cloud architecture in JSX. CReact figures out the dependencies, orchestrates the deployment, and keeps everything in sync.
+
+```tsx
+function App() {
+  return (
+    <VPC name="prod-vpc">
+      <Database name="users-db">
+        <API name="users-api">
+          <Monitoring />
+        </API>
+      </Database>
+    </VPC>
+  );
+}
+```
+
+That's it. No dependency graphs, no explicit ordering, no YAML. Just components that render to actual infrastructure.
+
+## The Problem
+
+Terraform and Pulumi are great, but they're static. You write a plan, run it, and hope nothing breaks. If you need dynamic orchestration - like deploying a database, waiting for its endpoint, then using that endpoint in your API config - you're writing bash scripts or custom tooling.
+
+CReact treats infrastructure like React treats UI. Components re-render when their dependencies change. Outputs flow naturally through context. The Reconciler figures out what actually needs to deploy.
+
+## What Makes It Different
+
+**It's reactive** - when a database finishes deploying and outputs its endpoint, components that depend on it automatically re-render and deploy. No manual dependency chains.
+
+**It's a compiler** - your JSX compiles to CloudDOM (basically an AST for infrastructure). You can diff it, version it, test it without cloud credentials. Only when you're ready does it materialize to real resources.
+
+**It's resilient** - every deployment is checkpointed and resumable. Crash halfway through? Resume from where you left off. The Reconciler only deploys what changed, like React's virtual DOM but for cloud resources.
+
+**It works with existing tools** - CReact doesn't replace Terraform or CDK. It orchestrates them. Wrap your Terraform modules as CReact components and compose them together.
+
+## Watch It Work
+
+Here's a real deployment - 22 resources across 3 regions, 6 reactive cycles, fully automatic:
+
+```bash
+$ creact dev --entry reactive-app.tsx --auto-approve
+
+Starting CReact development mode...
+Building initial state...
+Changes detected: 2 changes
+
+Planning changes for stack: optimized-reactive-app-stack
+──────────────────────────────────────────────────
++ 2 to create
+  + Analytics (Kinesis stream for API analytics)
+  + VPC (Network foundation)
+
+Plan: 2 to add, 0 to change, 0 to destroy
+Auto-approving changes...
+
+Applying changes...
+[MockCloud] ✅ All resources materialized
+Apply complete! Resources: 2 added, 0 changed, 0 destroyed
+Duration: 0.3s
+
+Reactive changes detected
++ 6 to create
+  + S3Bucket (Asset storage)
+  + SecurityGroup (Network security)
+  + Subnet × 4 (Multi-AZ subnets)
+
+Plan: 6 to add, 0 to change, 0 to destroy
+Reactive deployment cycle #2
+Apply complete! Resources: 6 added, 0 changed, 0 destroyed
+Duration: 0.1s
+
+Reactive changes detected
++ 4 to create
+  + ElastiCache (Redis cluster)
+  + CloudFront (CDN distribution)
+  + LoadBalancer (Application load balancer)
+  + RDSInstance (PostgreSQL database)
+
+Reactive deployment cycle #3
+Apply complete! Resources: 4 added, 0 changed, 0 destroyed
+Duration: 0.5s
+
+Reactive changes detected
++ 4 to create
+  + Lambda × 3 (Regional API handlers: us-east-1, eu-west-1, ap-southeast-1)
+  + Backup (Database backup vault)
+
+Reactive deployment cycle #4
+Apply complete! Resources: 4 added, 0 changed, 0 destroyed
+Duration: 0.5s
+
+Reactive changes detected
++ 3 to create
+  + ApiGateway × 3 (Regional API endpoints)
+
+Reactive deployment cycle #5
+Apply complete! Resources: 3 added, 0 changed, 0 destroyed
+Duration: 0.4s
+
+Reactive changes detected
++ 3 to create
+  + CloudWatch × 3 (Regional monitoring dashboards)
+
+Reactive deployment cycle #6
+Apply complete! Resources: 3 added, 0 changed, 0 destroyed
+Duration: 0.4s
+
+✅ Deployment complete: 22 resources across 6 reactive cycles
+Watching for changes... (Press Ctrl+C to stop)
+```
+
+**What happened:**
+
+VPC deployed first. When its outputs became available, subnets and security groups deployed in parallel. When those finished, database and cache deployed. When the database endpoint was ready, Lambdas deployed. When Lambdas got function ARNs, API Gateways deployed. When APIs were live, monitoring deployed.
+
+You didn't orchestrate anything manually. You just wrote JSX components that reference each other's outputs. CReact figured out the rest.
+
+## How It Works
+
+### JSX Compiles to CloudDOM
+
+```tsx
+<VPC name="app-vpc" cidr="10.0.0.0/16" />
+```
+
+becomes:
+
+```json
+{
+  "id": "app-vpc",
+  "construct": "VPC",
+  "props": { "cidr": "10.0.0.0/16" },
+  "outputs": {}
+}
+```
+
+CloudDOM is just a JSON tree. You can diff it like Git, version it, test it without touching AWS. It's the intermediate representation between your code and actual cloud resources.
+
+### The Reconciler Figures Out What Changed
+
+Before deploying anything, CReact diffs the previous CloudDOM against the new one. Creates, updates, deletes, replacements - all computed ahead of time. You get a Terraform-style plan but it's just comparing two data structures.
+
+### Deployment Is Checkpointed
+
+After each resource deploys, CReact saves a checkpoint. Crash halfway through? Run it again and it resumes from where it left off. No manual cleanup, no orphaned resources.
+
+### Outputs Trigger Re-renders
+
+When a resource finishes deploying, its outputs (endpoint, ARN, ID) become available. Any component that depends on those outputs automatically re-renders and creates new resources. It's like useEffect but for infrastructure.
+
+
+
+## Hooks
+
+### useInstance - Create Resources
+
+Creates cloud resources and provides access to their outputs:
+
+```tsx
+function DatabaseComponent() {
+  // Create database resource
+  const database = useInstance(Database, {
+    name: 'my-db',
+    engine: 'postgres'
+  });
+
+  // Access outputs after deployment
+  console.log(database.outputs?.endpoint); // "db.example.com:5432"
+
+  return <></>;
+}
+```
+
+**Key Behavior**: If any prop value is `undefined`, creates a placeholder node that doesn't deploy. When dependencies become available, component re-renders and creates the real resource.
+
+### useState - Persistent State
+
+Manages state that persists across deployments:
+
+```tsx
+function App() {
+  // State survives deployments (stored in backend)
+  const [deployCount, setDeployCount] = useState(0);
+  const [appVersion] = useState('1.0.0');
+
+  // Update state (takes effect next deployment)
+  setDeployCount(prev => (prev || 0) + 1);
+
+  return <></>;
+}
+```
+
+**Advanced**: Can bind to provider outputs for reactivity:
+
+```tsx
+function DatabaseComponent() {
+  const db = useInstance(Database, { name: 'my-db' });
+
+  // This triggers re-renders when db.outputs.endpoint changes
+  const [endpoint, setEndpoint] = useState(db.outputs?.endpoint);
+
+  return <></>;
+}
+```
+
+### useContext - Share Dependencies
+
+Shares data between components with reactivity when containing outputs:
+
+```tsx
+const DatabaseContext = createContext<{ endpoint?: string }>({});
+
+function DatabaseProvider({ children }) {
+  const db = useInstance(Database, { name: 'my-db' });
+
+  return (
+    <DatabaseContext.Provider value={{
+      endpoint: db.outputs?.endpoint  // Makes context reactive
+    }}>
+      {children}
+    </DatabaseContext.Provider>
+  );
+}
+
+function ApiConsumer() {
+  const { endpoint } = useContext(DatabaseContext); // Re-renders when endpoint available
+
+  const api = useInstance(ApiGateway, {
+    dbUrl: endpoint  // Triggers re-render when endpoint changes
+  });
+
+  return <></>;
+}
+```
+
+## Reactivity Mechanisms
+
+CReact implements multiple interconnected reactivity systems:
+
+1. **useState Binding**: `useState` can bind to provider outputs, triggering re-renders when outputs change
+2. **Context Dependency Tracking**: Contexts containing outputs trigger re-renders in consuming components
+3. **Output Change Detection**: Post-deployment effect system detects when provider outputs change
+4. **Selective Re-rendering**: Only components affected by changes re-render
+
+## Deployment Orchestration
+
+### Reactive Deployment Cycles
+
+```tsx
+function MultiLayerApp() {
+  return (
+    <NetworkStack>        {/* Layer 1: Deploy VPC first */}
+      <DatabaseStack>     {/* Layer 2: Deploy DB/cache when VPC ready */}
+        <StorageStack>    {/* Layer 3: Deploy S3/CDN when network ready */}
+          <ApiStack>      {/* Layer 4: Deploy APIs when all deps ready */}
+            <MonitoringStack /> {/* Layer 5: Deploy monitoring last */}
+          </ApiStack>
+        </StorageStack>
+      </DatabaseStack>
+    </NetworkStack>
+  );
+}
+```
+
+**Deployment Flow**:
+1. **Initial Render**: All components create resource references
+2. **Wave 1**: Network resources deploy (no dependencies)
+3. **Wave 2**: Data resources deploy (depend on network outputs)
+4. **Wave 3**: Storage resources deploy (depend on network outputs)
+5. **Wave 4**: API resources deploy (depend on data + storage outputs)
+6. **Wave 5**: Monitoring resources deploy (depend on API outputs)
+
+## Provider Implementation
+
+### Cloud Provider Example
+
+```tsx
+class AWSProvider implements ICloudProvider {
+  async materialize(resources: CloudDOMNode[]): Promise<void> {
+    for (const resource of resources) {
+      if (resource.construct?.name === 'Database') {
+        const db = await this.createRDSInstance(resource.props);
+        resource.outputs = {
+          endpoint: db.endpoint,
+          connectionUrl: db.connectionString
+        };
+      }
+      // Handle other resource types...
+    }
+  }
+}
+```
+
+### Backend Provider Example
+
+```tsx
+class S3BackendProvider implements IBackendProvider {
+  async getState(stackName: string): Promise<any> {
+    const state = await this.s3.getObject({
+      Bucket: 'my-state-bucket',
+      Key: `${stackName}.json`
+    }).promise();
+
+    return JSON.parse(state.Body.toString());
+  }
+
+  async saveState(stackName: string, state: any): Promise<void> {
+    await this.s3.putObject({
+      Bucket: 'my-state-bucket',
+      Key: `${stackName}.json`,
+      Body: JSON.stringify(state)
+    }).promise();
+  }
+}
+```
+
+## Real-World Example
+
+Here's how the 5-layer enterprise application from the examples works:
+
+```tsx
+function EnterpriseApp() {
+  return (
+    <NetworkProvider>     {/* VPC, subnets, security groups */}
+      <DatabaseProvider>  {/* Database + cache */}
+        <StorageProvider> {/* S3 + CDN */}
+          <ApiProvider>   {/* APIs + load balancer */}
+            <MonitoringProvider /> {/* Analytics + backups */}
+          </ApiProvider>
+        </StorageProvider>
+      </DatabaseProvider>
+    </NetworkProvider>
+  );
+}
+
+// Each provider component:
+function NetworkProvider({ children }) {
+  const vpc = useInstance(VPC, { cidr: '10.0.0.0/16' });
+
+  return (
+    <NetworkContext.Provider value={{ vpcId: vpc.outputs?.vpcId }}>
+      {children}
+    </NetworkContext.Provider>
+  );
+}
+
+function DatabaseProvider({ children }) {
+  const { vpcId } = useContext(NetworkContext);
+
+  const db = useInstance(Database, { vpcId });
+  const cache = useInstance(Redis, { vpcId });
+
+  return (
+    <DatabaseContext.Provider value={{
+      dbUrl: db.outputs?.endpoint,
+      cacheUrl: cache.outputs?.endpoint
+    }}>
+      {children}
+    </DatabaseContext.Provider>
+  );
+}
+```
+
+## Installation & Usage
+
+```bash
+# Deploy your infrastructure
+creact deploy --entry my-app.tsx
+
+# Development mode with hot reload
+creact dev --entry my-app.tsx --auto-approve
+
+# Preview changes
+creact plan --entry my-app.tsx
+```
+

package/dist/cli/commands/BuildCommand.d.ts

@@ -0,0 +1,40 @@
+/**
+
+ * Licensed under the Apache License, Version 2.0 (the "License");
+
+ * you may not use this file except in compliance with the License.
+
+ * You may obtain a copy of the License at
+
+ *
+
+ *     http://www.apache.org/licenses/LICENSE-2.0
+
+ *
+
+ * Unless required by applicable law or agreed to in writing, software
+
+ * distributed under the License is distributed on an "AS IS" BASIS,
+
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+
+ * See the License for the specific language governing permissions and
+
+ * limitations under the License.
+
+ *
+
+ * Copyright 2025 Daniel Coutinho Ribeiro
+
+ */
+/**
+ * Build Command - builds CloudDOM from entry file
+ */
+import { BaseCommand, CommandResult } from '../core/BaseCommand';
+export declare class BuildCommand extends BaseCommand {
+    getName(): string;
+    getDescription(): string;
+    execute(): Promise<CommandResult>;
+    private printVerboseOutput;
+    private countResources;
+}