alchemy 0.1.4 → 0.1.5

package/test/aws/role.test.ts

@@ -5,8 +5,8 @@ import {
 } from "@aws-sdk/client-iam";
 import { describe, expect, test } from "bun:test";
 import { apply } from "../../src/apply";
-import type { PolicyDocument } from "../../src/components/aws";
-import { Role, type RoleProps } from "../../src/components/aws/role";
+import type { PolicyDocument } from "../../src/aws/policy";
+import { Role, type RoleProps } from "../../src/aws/role";
 import { destroy } from "../../src/destroy";
 
 // Verify role was deleted

package/test/aws/table.test.ts

@@ -5,7 +5,7 @@ import {
 } from "@aws-sdk/client-dynamodb";
 import { describe, expect, test } from "bun:test";
 import { apply } from "../../src/apply";
-import { Table } from "../../src/components/aws/table";
+import { Table } from "../../src/aws/table";
 import { destroy } from "../../src/destroy";
 
 const dynamo = new DynamoDBClient({});

package/test/esbuild.test.ts

@@ -2,8 +2,8 @@ import { describe, expect, test } from "bun:test";
 import fs from "node:fs";
 import path from "node:path";
 import { apply } from "../src/apply";
-import { Bundle } from "../src/components/esbuild";
 import { destroy } from "../src/destroy";
+import { Bundle } from "../src/esbuild";
 
 const __dirname = path.dirname(new URL(import.meta.url).pathname);
 

package/test/scope.test.ts

@@ -1,9 +1,9 @@
 import { describe, expect, it } from "bun:test";
 import { apply } from "../src/apply";
-import type { PolicyDocument } from "../src/components/aws/policy";
-import { Role } from "../src/components/aws/role";
-import { File } from "../src/components/fs";
+import type { PolicyDocument } from "../src/aws/policy";
+import { Role } from "../src/aws/role";
 import { destroy } from "../src/destroy";
+import { File } from "../src/fs";
 import { rootScope } from "../src/global";
 import { type Context, Resource } from "../src/resource";
 import { Scope, getScope, withScope } from "../src/scope";

package/test/stripe/stripe.test.ts

@@ -0,0 +1,136 @@
+import { describe, expect, test } from "bun:test";
+import Stripe from "stripe";
+import { apply } from "../../src/apply";
+import { destroy } from "../../src/destroy";
+import { Price } from "../../src/stripe/price";
+import { Product } from "../../src/stripe/product";
+import { WebhookEndpoint } from "../../src/stripe/webhook";
+
+const stripeApiKey = process.env.STRIPE_API_KEY;
+if (!stripeApiKey) {
+  throw new Error("STRIPE_API_KEY environment variable is required");
+}
+
+// Initialize a Stripe client for verification
+const stripe = new Stripe(stripeApiKey);
+
+describe("Stripe Resources", () => {
+  test("create and destroy stripe resources", async () => {
+    // Create a test product
+    const product = new Product("alchemy-test-product", {
+      name: "Alchemy Test Product",
+      description: "A product created by Alchemy tests",
+    });
+
+    // Apply the product first to get its ID
+    const productOutput = await apply(product);
+    expect(productOutput.id).toBeTruthy();
+    expect(productOutput.name).toBe("Alchemy Test Product");
+
+    // Verify with Stripe API
+    const stripeProduct = await stripe.products.retrieve(productOutput.id);
+    expect(stripeProduct.name).toBe("Alchemy Test Product");
+
+    // Create a price for the product
+    const price = new Price("alchemy-test-price", {
+      product: productOutput.id,
+      currency: "usd",
+      unitAmount: 1500, // $15.00
+      recurring: {
+        interval: "month",
+      },
+    });
+
+    // Apply the price
+    const priceOutput = await apply(price);
+    expect(priceOutput.id).toBeTruthy();
+    expect(priceOutput.unitAmount).toBe(1500);
+    expect(priceOutput.recurring?.interval).toBe("month");
+
+    // Verify with Stripe API
+    const stripePrice = await stripe.prices.retrieve(priceOutput.id);
+    expect(stripePrice.unit_amount).toBe(1500);
+
+    // Create a webhook endpoint
+    const webhook = new WebhookEndpoint("alchemy-test-webhook", {
+      url: "https://example.com/alchemy-webhook",
+      enabledEvents: [
+        "checkout.session.completed",
+        "customer.subscription.created",
+      ],
+      description: "Webhook for Alchemy tests",
+    });
+
+    // Apply the webhook
+    const webhookOutput = await apply(webhook);
+    expect(webhookOutput.id).toBeTruthy();
+    expect(webhookOutput.url).toBe("https://example.com/alchemy-webhook");
+    expect(webhookOutput.secret).toBeTruthy();
+
+    // Verify with Stripe API
+    const stripeWebhook = await stripe.webhookEndpoints.retrieve(
+      webhookOutput.id,
+    );
+    expect(stripeWebhook.url).toBe("https://example.com/alchemy-webhook");
+
+    // Clean up resources
+    console.log("Cleaning up Stripe resources...");
+    await destroy(webhook);
+    await destroy(price);
+    await destroy(product);
+
+    // Verify clean up
+    await assertProductDeactivated(productOutput.id);
+    await assertPriceDeactivated(priceOutput.id);
+    await assertWebhookDeleted(webhookOutput.id);
+  });
+});
+
+// Helper functions for verification
+async function assertProductDeactivated(productId: string) {
+  try {
+    const product = await stripe.products.retrieve(productId);
+    // Products are deactivated, not deleted
+    expect(product.active).toBe(false);
+  } catch (error) {
+    // If product is not found, that's also acceptable
+    if (
+      error instanceof Stripe.errors.StripeError &&
+      error.code === "resource_missing"
+    ) {
+      return;
+    }
+    throw error;
+  }
+}
+
+async function assertPriceDeactivated(priceId: string) {
+  try {
+    const price = await stripe.prices.retrieve(priceId);
+    // Prices are deactivated, not deleted
+    expect(price.active).toBe(false);
+  } catch (error) {
+    // If price is not found, that's also acceptable
+    if (
+      error instanceof Stripe.errors.StripeError &&
+      error.code === "resource_missing"
+    ) {
+      return;
+    }
+    throw error;
+  }
+}
+
+async function assertWebhookDeleted(webhookId: string) {
+  try {
+    await stripe.webhookEndpoints.retrieve(webhookId);
+    throw new Error("Webhook still exists");
+  } catch (error) {
+    // Webhook should be deleted, so we expect a resource_missing error
+    if (error instanceof Stripe.errors.StripeError) {
+      expect(error.code).toBe("resource_missing");
+    } else {
+      throw error;
+    }
+  }
+}

package/README.md

@@ -1,324 +0,0 @@
-# Alchemy
-
-Alchemy is a JS-native, embeddable library for the materialization of resource graphs. From Infrastructure-as-Code (IaC) to code generation, Alchemy provides the fundamental building blocks for modeling resources that are Created, Updated and Deleted automatically.
-
-Unlike similar tools like Pulumi, Terraform, and CloudFormation, Alchemy is implemented in pure ESM-native TypeScript with zero dependencies. It can run in any JavaScript runtime, including the browser.
-
-[![Demo](./alchemy.gif)](./alchemy.gif)
-
-# Features
-
-- **JS-native** - no second language, toolchains, dependencies, processes, services, etc. to lug around.
-- **ESM-native** - built exclusively on ESM, with a slight preference for modern JS runtimes like Bun.
-- **Embeddable** - runs in any JavaScript/TypeScript environment, including the browser!
-- **Extensible** - implement your own resources with a simple function.
-- **AI-first** - alchemy actively encourages you to use LLMs to create/copy/fork/modify resources to fit your needs. No more waiting around for a provider to be implemented, just do it yourself in a few minutes.
-- **No dependencies** - the `alchemy` core package has 0 required dependencies.
-- **No service** - state files are stored locally in your project and can be easily inspected, modified, checked into your repo, etc.
-- **No strong opinions** - structure your codebase however you want, store state anywhere - we don't care!
-
-# Examples
-
-- LLM-based code generation of all 200+ AWS CloudFormation resources: [examples/generate-aws-cfn/gen.ts](./examples/generate-aws-cfn/gen.ts)
-- Deploy an AWS Lambda Function with a DynamoDB Table and IAM Role: [examples/deploy-aws/app.ts](./examples/deploy-aws/)
-- Generate a TODO application from a Markdown document: [examples/markdown-program/index.md](./examples/markdown-program/)
-
-# Getting Started
-
-An alchemy "app" (if you want to call it that) is just an ordinary TypeScript or JavaScript script. Once you've installed the `alchemy` package, you can start using it however you want.
-
-```bash
-# I recommend bun, but you can use any JavaScript runtime.
-bun add alchemy
-```
-
-Usually, you'll want to create a script where you'll define your resources.
-
-```ts
-import { Role } from "alchemy/aws";
-
-const role = new Role("my-role", {
-  name: "my-role",
-  //..
-});
-```
-
-Then, call `alchemize` at the end to trigger the Create/Update/Delete lifecycle.
-
-```ts
-await alchemize();
-```
-
-Finally, run your script.
-
-```sh
-bun ./my-app.ts
-```
-
-You'll notice some files show up in your repo:
-
-```
-.alchemy/
-  - sam/
-    - my-role.json
-```
-
-Go ahead, click on one and take a look. Here's how my role looks:
-
-```jsonc
-{
-  "provider": "iam::Role",
-  "data": {},
-  "deps": [],
-  "status": "updated",
-  "output": {
-    "roleName": "alchemy-api-lambda-role"
-    // ..
-  },
-  "inputs": [
-    {
-      "roleName": "alchemy-api-lambda-role",
-      "assumeRolePolicy": {
-        "Version": "2012-10-17"
-        // ..
-      }
-    }
-  ]
-}
-```
-
-> [!TIP]
-> Alchemy goes to great effort to be fully transparent. State is just a JSON file, nothing more. You can inspect it, modify it, commit it to your repo, etc.
-
-## `alchemize`
-
-Calling `alchemize` will create new resources, update modified resources and then delete "orphaned" resources at the end.
-
-This is equivalent to `terraform apply`, `pulumi up`, `cdk deploy`, etc. except really fast and in your control.
-
-## Creating a Resource Provider
-
-Adding new resources is the whole point of Alchemy, and is therefore very simple.
-
-A Resource provider is just a function with a globally unique name, e.g. `dynamo::Table`, and an implementation of the Create, Update, Delete lifecycle operations.
-
-E.g. below we show what a simple `dynamo::Table` provider might look like.
-
-> [!NOTE]
-> See [table.ts](./alchemy/src/components/aws/table.ts) for the full implementation.
-
-```ts
-interface TableInputs {
-  name: string;
-  //..
-}
-interface TableOutput {
-  tableArn: string;
-}
-class Table extends Resource(
-  "dynamo::Table",
-  async (ctx: Context<TableOutput>, inputs: TableInputs) => {
-    if (ctx.event === "create") {
-      // create logic
-    } else if (ctx.event === "update") {
-      // update logic
-    } else if (ctx.event === "delete") {
-      // delete logic
-    }
-    // ..
-    return output;
-  }
-) {}
-```
-
-> [!TIP]
-> Use Cursor or an LLM like Claude/OpenAI to generate the implementation of your resource. I think you'll be pleasantly surprised at how well it works, especially if you provide the API reference docs in your context.
-
-That's it! Now you can instantiate tables in your app.
-
-```ts
-const table = new Table("items", {
-  name: "items",
-  //..
-});
-
-table.tableArn; // Output<string>
-```
-
-You may have noticed the odd pattern of extending the result of a function call, `extends Resource(..)`. This is called the "mix-in" pattern and is optional. You are free to just use a `const` instead:
-
-```ts
-const Table = Resource("dynamo::Table", async (ctx, inputs) => {
-  //..
-});
-
-const table = new Table("items", {
-  name: "items",
-  //..
-});
-```
-
-> [!TIP]
-> I recommend using a class so each resource has a type, e.g. `Table`, and a place to add helper/utility methods. Totally optional, though. Knock yourself out.
-
-## Lazy Outputs
-
-A Resource is evaluated lazily (not when you call `new`), so you can't immediately access the value of a property like `tableArn` or `functionArn`. Instead you reference properties using the `Output<T>` interface.
-
-```ts
-const table = new Table("my-table", { .. });
-
-const tableArn = table.tableArn; // Output<string>
-```
-
-Outputs can be chained explicitly and implicitly:
-
-1. _Explicitly_ with `.apply`
-
-```ts
-const tableArn: Output<string> = table.tableArn.apply((arn: string) =>
-  // do something with the arn string value
-  arn.replace("table", "arn:aws:dynamodb:")
-);
-```
-
-2. _Implicitly_ chained
-
-```ts
-const tableArn = table.attributeDefinitions[0].attributeName; // Output<string>
-// equivalent to:
-// table.apply(t => t.attributeDefinitions[0].attributeName);
-```
-
-> [!NOTE]
-> Output is inspired by Pulumi, with a little extra added sugar.
-
-## `apply` and `destroy`
-
-Calling `alchemize` is optional. Any object in your graph (`Resource` or `Output<T>`) can be "applied" or "destroyed" individually and programmatically.
-
-Say, you've got some two resources, a `Role` and a `Function`.
-
-```ts
-const role = new Role("my-role", {
-  name: "my-role",
-  //..
-});
-
-const func = new Function("my-function", {
-  name: "my-function",
-  role: role.roleArn,
-  //..
-});
-```
-
-Each of these Resources is known as a "sub-graph".
-
-In this case we have `Role` (a 1-node graph, `Role`), and `Function` (a 2-node graph, `Role → Function`).
-
-Each sub-graph can be "applied" or "destroyed" individually using the `apply` and `destroy` functions:
-
-```ts
-import { apply, destroy } from "alchemy";
-
-// will create Role and then Function (in that order)
-const { functionArn } = await apply(func);
-
-// you can destroy it right after if you want ☠️
-await destroy(func); // will delete just the Function
-
-// destroy deletes the resource and any downstream dependencies
-// so, if you want to delete Role AND Function, you should call destroy(role)
-await destroy(role); // will delete Role and then Function
-```
-
-## Destroying the app
-
-To destroy the whole app (aka. the whole graph), you can call `alchemize` with the `mode: "destroy"` option. This will delete all resources in the specified or default stage.
-
-```ts
-await alchemize({ mode: "destroy", stage: <optional> });
-```
-
-> [!TIP]
-> Alchemy is designed to have the minimum number of opinions as possible. This "embeddable" design is so that you can implement your own tools around Alchemy, e.g. a CLI or UI, instead of being stuck with a specific tool.
->
-> ```ts
-> await alchemize({
->   // decide the mode/stage however you want, e.g. a CLI parser
->   mode: process.argv[2] === "destroy" ? "destroy" : "up",
->   stage: process.argv[3],
-> });
-> ```
-
-## "Stage" and State
-
-> [!NOTE]
-> Stage is inspired by [SST](https://sst.dev)'s stage concept.
-
-Alchemy supports a "stage" concept to help isolate different environments from each other. E.g. a `"user"` or `"dev"` or `"prod"` stage.
-
-By default, the stage is assumed to be your user name (a sensible default for local development).
-
-To override the stage, you have three options:
-
-1. Pass the `stage` option to `alchemize`/`apply`/`destroy` (recommended)
-
-```ts
-// alchemize the entire app
-await alchemize({ stage: "production" });
-
-// apply a single resource
-await apply(func, { stage: "production" });
-```
-
-2. Config in `./alchemy.ts` (up to you if you want to have a global config). See the [alchemy.ts section](#global-values-and-the-alchemy-ts-config-file) for more details.
-
-```ts
-export default {
-  defaultStage: "production",
-};
-```
-
-3. Set the `ALCHEMY_STAGE` environment variable (not recommended, but available as an escape hatch)
-
-```sh
-ALCHEMY_STAGE=production bun ./my-app.ts
-```
-
-Each Resource "provider" can access the stage it's being deployed to via the `ctx.stage` property.
-
-```ts
-class Table extends Resource("dynamo::Table", async (ctx, inputs) => {
-  ctx.stage; // "production"
-});
-```
-
-> [!CAUTION]
-> It is up to you to ensure that the physical names of resources don't conflict - alchemy does not (yet) offer any help or opinions here. You must decide on physical names, but you're free to add name generation logic to your resources if you so desire.
->
-> ```ts
-> class Table extends Resource("dynamo::Table", async (ctx, inputs) => {
->   const tableName = `${ctx.stage}-${inputs.tableName}`;
->
->   // ..
-> });
-> ```
-
-## Global values and the `alchemy.ts` config file.
-
-Alchemy looks for a `${cwd}/alchemy.ts` file and imports it if it finds it. This can be useful for emulating SST's `sst.config.ts` file as a convention for global configuration.
-
-It supports overriding the `defaultStage` (instead of defaulting to your username) and providing a custom `stateStore` (instead of writing to the local file system).
-
-```ts
-import type { Config } from "alchemy";
-
-export default {
-  defaultStage: "dev",
-  stateStore: myCustomStateStore,
-} satisfies Config;
-```
-
-> [!NOTE]
-> See [global.ts](./alchemy/src/global.ts).

package/src/typescript/install-packages.ts

@@ -1,50 +0,0 @@
-import { tool } from "ai";
-import { exec } from "child_process";
-import { promisify } from "util";
-import { z } from "zod";
-
-const execAsync = promisify(exec);
-
-export const installPackages = tool({
-  description: "Installs one or more packages using bun add",
-  parameters: z.object({
-    packages: z.array(z.string()).describe("Array of package names to install"),
-    isDev: z
-      .boolean()
-      .optional()
-      .describe("Whether to install as dev dependencies"),
-    cwd: z
-      .string()
-      .optional()
-      .describe("Working directory where to run the install command"),
-  }),
-  execute: async ({ packages, isDev = false, cwd = process.cwd() }) => {
-    if (packages.length === 0) {
-      throw new Error("No packages specified for installation");
-    }
-
-    const command = `bun add ${isDev ? "-D " : ""}${packages.join(" ")}`;
-
-    try {
-      console.log(`Running command: ${command}`);
-      const { stdout, stderr } = await execAsync(command, { cwd });
-
-      if (stderr) {
-        console.error("Installation stderr:", stderr);
-      }
-
-      return {
-        success: true,
-        command,
-        output: stdout,
-        packages,
-        type: isDev ? "dev" : "regular",
-      };
-    } catch (error: any) {
-      console.error("Installation error:", error);
-      throw new Error(
-        `Failed to install packages: ${error?.message || String(error)}`,
-      );
-    }
-  },
-});