@eventcatalog/create-eventcatalog 4.3.8 → 4.3.10

package/dist/index.js

@@ -25092,7 +25092,7 @@ var import_fs2 = require("fs");
 var actualFS = __toESM(require("fs"), 1);
 var import_promises = require("fs/promises");
 
-// ../../node_modules/.pnpm/minipass@7.1.2/node_modules/minipass/dist/esm/index.js
+// ../../node_modules/.pnpm/minipass@7.1.3/node_modules/minipass/dist/esm/index.js
 var import_node_events = require("events");
 var import_node_stream = __toESM(require("stream"), 1);
 var import_node_string_decoder = require("string_decoder");
@@ -25173,7 +25173,7 @@ var PipeProxyErrors = class extends Pipe {
   }
   constructor(src, dest, opts) {
     super(src, dest, opts);
-    this.proxyErrors = (er) => dest.emit("error", er);
+    this.proxyErrors = (er) => this.dest.emit("error", er);
     src.on("error", this.proxyErrors);
   }
 };
@@ -25889,6 +25889,8 @@ var Minipass = class extends import_node_events.EventEmitter {
       return: stop,
       [Symbol.asyncIterator]() {
         return this;
+      },
+      [Symbol.asyncDispose]: async () => {
       }
     };
   }
@@ -25924,6 +25926,8 @@ var Minipass = class extends import_node_events.EventEmitter {
       return: stop,
       [Symbol.iterator]() {
         return this;
+      },
+      [Symbol.dispose]: () => {
       }
     };
   }
@@ -29831,7 +29835,7 @@ var import_os2 = __toESM(require("os"));
 var package_default = {
   name: "@eventcatalog/create-eventcatalog",
   description: "Create EventCatalog with one command",
-  version: "4.3.8",
+  version: "4.3.10",
   license: "MIT",
   bin: {
     "create-catalog": "./dist/index.js"

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@eventcatalog/create-eventcatalog",
   "description": "Create EventCatalog with one command",
-  "version": "4.3.8",
+  "version": "4.3.10",
   "license": "MIT",
   "bin": {
     "create-catalog": "./dist/index.js"

package/templates/default/domains/Catalog/index.mdx

@@ -54,6 +54,12 @@ The **Catalog** domain is responsible for the lifecycle of every product Acme In
 
 The **Product Catalog System** is the authoritative source of product data. Whenever a product is created, updated or deleted it publishes a domain event. The **Search System** subscribes to those events, keeps its search index in sync, and exposes a search API so other teams never have to query the catalog database directly.
 
+## Architecture Graph
+
+Where Catalog sits in the wider architecture — its systems and messages, and the neighbouring domains it talks to.
+
+<ArchitectureGraph />
+
 The diagram below shows the domain's systems, how they relate, and the people who interact with them.
 
 <ContextDiagram />

package/templates/default/domains/Catalog/systems/product-catalog-system/containers/product-database/index.mdx

@@ -2,6 +2,8 @@
 id: product-database
 name: Product Database
 version: 1.0.0
+owners:
+  - product-platform
 summary: PostgreSQL database that is the system of record for all product data.
 container_type: database
 technology: postgres@16

package/templates/default/domains/Catalog/systems/search-system/containers/search-index/index.mdx

@@ -2,6 +2,8 @@
 id: search-index
 name: Search Index
 version: 1.0.0
+owners:
+  - search-platform
 summary: The denormalised, search-optimised index of products that powers product search.
 container_type: searchIndex
 technology: opensearch@2

package/templates/default/domains/Customer/index.mdx

@@ -59,9 +59,3 @@ The **Customer Management System** owns customer profile data — it accepts reg
 The systems in this domain, how they relate, and the people who interact with them.
 
 <ContextDiagram />
-
-## Resource Diagram
-
-The components that make up this domain.
-
-<NodeGraph />

package/templates/default/domains/Customer/systems/customer-management-system/containers/customer-database/index.mdx

@@ -2,6 +2,8 @@
 id: customer-database
 name: Customer Database
 version: 1.0.0
+owners:
+  - customer-platform
 summary: PostgreSQL database that is the system of record for all customer profile data.
 container_type: database
 technology: postgres@16

package/templates/default/domains/Customer/systems/identity-provider/containers/user-directory/index.mdx

@@ -2,6 +2,8 @@
 id: user-directory
 name: User Directory
 version: 1.0.0
+owners:
+  - customer-platform
 summary: The directory of customer credentials and identities — the source of truth for authentication.
 container_type: database
 technology: postgres@16

package/templates/default/domains/Fulfilment/index.mdx

@@ -75,9 +75,3 @@ When an order is completed, the **Warehouse System** picks and packs it, having
 The systems in this domain, how they relate, and the people who interact with them.
 
 <ContextDiagram />
-
-## Resource Diagram
-
-The components that make up this domain.
-
-<NodeGraph />

package/templates/default/domains/Fulfilment/systems/inventory-system/containers/inventory-database/index.mdx

@@ -2,6 +2,8 @@
 id: inventory-database
 name: Inventory Database
 version: 1.0.0
+owners:
+  - fulfilment-platform
 summary: PostgreSQL database that is the system of record for stock levels and reservations.
 container_type: database
 technology: postgres@16

package/templates/default/domains/Fulfilment/systems/warehouse-system/containers/warehouse-database/index.mdx

@@ -2,6 +2,8 @@
 id: warehouse-database
 name: Warehouse Database
 version: 1.0.0
+owners:
+  - fulfilment-platform
 summary: PostgreSQL database that stores picking jobs and their status.
 container_type: database
 technology: postgres@16

package/templates/default/domains/Ordering/index.mdx

@@ -68,3 +68,9 @@ The systems in this domain, how they relate, and the people who interact with th
 The components that make up this domain.
 
 <NodeGraph />
+
+## Architecture Graph
+
+Where Ordering sits in the wider architecture — its systems and messages, and the neighbouring domains it talks to.
+
+<ArchitectureGraph />

package/templates/default/domains/Ordering/systems/checkout-system/index.mdx

@@ -55,3 +55,9 @@ The services and messages that make up this system.
 - [[command\|reserve-inventory]] — reserve stock for the items in the cart.
 - [[command\|authorize-payment]] — authorize payment for the order total.
 - [[command\|create-order]] — create the order in the Order Management System.
+
+## Architecture Graph
+
+The checkout system's neighbourhood in the wider architecture.
+
+<ArchitectureGraph />

package/templates/default/domains/Ordering/systems/order-management-system/containers/order-database/index.mdx

@@ -2,6 +2,8 @@
 id: order-database
 name: Order Database
 version: 1.0.0
+owners:
+  - ordering-platform
 summary: PostgreSQL database that is the system of record for orders and their items.
 container_type: database
 technology: postgres@16

package/templates/default/domains/Payments/index.mdx

@@ -67,3 +67,9 @@ The **Payment Processing System** is the internal orchestrator. When the Orderin
 The systems in this domain, how they relate, and the people who interact with them.
 
 <ContextDiagram />
+
+## Architecture Graph
+
+Where Payments sits in the wider architecture — its systems and messages, and the neighbouring domains it talks to.
+
+<ArchitectureGraph />

package/templates/default/domains/Payments/systems/payment-processing-system/containers/payment-database/index.mdx

@@ -2,6 +2,8 @@
 id: payment-database
 name: Payment Database
 version: 1.0.0
+owners:
+  - payments-platform
 summary: PostgreSQL database that is the system of record for payments and refunds.
 container_type: database
 technology: postgres@16

package/templates/default/domains/Payments/systems/payment-processing-system/services/PaymentAPI/index.mdx

@@ -46,6 +46,12 @@ The **Payment API** is the entry point to the Payment Processing System. It rece
 
 <NodeGraph />
 
+## Architecture Graph
+
+How PaymentAPI connects to the rest of the catalog — the messages it exchanges and the systems around it.
+
+<ArchitectureGraph />
+
 <MessageTable format="all" limit={8} />
 
 <Footer />

package/templates/default/domains/Reviews/containers/rating-cache/index.mdx

@@ -2,6 +2,8 @@
 id: rating-cache
 name: Rating Cache
 version: 1.0.0
+owners:
+  - reviews-platform
 summary: Redis cache that serves each product's aggregate star rating with low latency.
 container_type: cache
 technology: redis@7

package/templates/default/domains/Reviews/containers/review-database/index.mdx

@@ -2,6 +2,8 @@
 id: review-database
 name: Review Database
 version: 1.0.0
+owners:
+  - reviews-platform
 summary: PostgreSQL database that is the system of record for reviews and their moderation state.
 container_type: database
 technology: postgres@16

package/templates/default/domains/Shopping/index.mdx

@@ -59,9 +59,3 @@ The **Cart System** owns the customer's cart and the checkout flow. When pricing
 The systems in this domain, how they relate, and the people who interact with them.
 
 <ContextDiagram />
-
-## Resource Diagram
-
-The components that make up this domain.
-
-<NodeGraph />

package/templates/default/domains/Shopping/systems/cart-system/containers/cart-database/index.mdx

@@ -2,6 +2,8 @@
 id: cart-database
 name: Cart Database
 version: 1.0.0
+owners:
+  - shopping-platform
 summary: PostgreSQL database that is the system of record for shopping carts and their items.
 container_type: database
 technology: postgres@16

package/templates/default/domains/Shopping/systems/promotion-system/containers/promotion-database/index.mdx

@@ -2,6 +2,8 @@
 id: promotion-database
 name: Promotion Database
 version: 1.0.0
+owners:
+  - shopping-platform
 summary: PostgreSQL store of promotion and discount rules.
 container_type: database
 technology: postgres@16

package/templates/default/pages/homepage.astro

@@ -2,8 +2,8 @@
 import { getCollection } from 'astro:content';
 
 // EventCatalog injects its components via Astro.props.components. Destructure the ones
-// this landing page uses (including the SystemContextMap embed).
-const { Tile, Tiles, SystemContextMap } = Astro.props.components;
+// this landing page uses (including the ArchitectureGraph and SystemContextMap embeds).
+const { Tile, Tiles, SystemContextMap, ArchitectureGraph } = Astro.props.components;
 
 // Count the catalog's top-level resources. We filter out versioned/ entries so each
 // resource is counted once (by its latest version).
@@ -49,6 +49,16 @@ const stats = [
     }
   </div>
 
+  {/* Architecture graph */}
+  <h2 class="text-2xl font-semibold text-[rgb(var(--ec-page-text))] mt-12 mb-2">Architecture</h2>
+  <p class="text-[rgb(var(--ec-page-text-muted))] font-light mb-2">
+    Every resource in the catalog and the relationships between them.
+  </p>
+</div>
+
+<ArchitectureGraph lens="domains" lensPicker="true" />
+
+<div class="not-prose">
   {/* System context map */}
   <h2 class="text-2xl font-semibold text-[rgb(var(--ec-page-text))] mt-12 mb-2">System context map</h2>
   <p class="text-[rgb(var(--ec-page-text-muted))] font-light mb-2">