@eventcatalog/create-eventcatalog 4.2.3 → 4.2.5

package/LICENSE

@@ -0,0 +1,28 @@
+MIT License
+
+Copyright (c) 2022-2026 boyney123
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+---
+
+Note: Source code within `packages/core/eventcatalog/src/enterprise/` is
+licensed under the EventCatalog Commercial License and is NOT covered by the
+MIT License above. See `packages/core/eventcatalog/src/enterprise/LICENSE`
+for the full terms.

package/dist/index.js

@@ -29808,7 +29808,8 @@ var import_os2 = __toESM(require("os"));
 var package_default = {
   name: "@eventcatalog/create-eventcatalog",
   description: "Create EventCatalog with one command",
-  version: "4.2.3",
+  version: "4.2.5",
+  license: "MIT",
   bin: {
     "create-catalog": "./dist/index.js"
   },
@@ -29910,6 +29911,7 @@ var installTemplate = async ({
       start: "eventcatalog start",
       preview: "eventcatalog preview",
       generate: "eventcatalog generate",
+      export: "eventcatalog export",
       lint: "eventcatalog-linter",
       test: 'echo "Error: no test specified" && exit 1'
     }

package/package.json

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

package/templates/amazon-api-gateway/gitignore

@@ -24,4 +24,6 @@ yarn-error.log*
 .eventcatalog-core
 
 .env
-.env-*
+.env-*
+
+exports/*

package/templates/asyncapi/README-template.md

@@ -1 +1,55 @@
 # My Event Catalog
+
+Welcome to your new catalog, powered by [EventCatalog](https://www.eventcatalog.dev) — the open-source documentation tool for event-driven architectures.
+
+## Getting Started
+
+```sh
+npm run dev
+```
+
+Open [http://localhost:3000](http://localhost:3000) to see your catalog.
+
+You can start editing your catalog by adding **domains**, **services**, and **messages** to this project. Each resource is a folder with an `index.md` file containing frontmatter metadata and markdown content.
+
+## What Can You Do?
+
+- **Document services** — define producers and consumers with their schemas
+- **Map events, commands & queries** — capture every message flowing through your system
+- **Organize with domains** — group resources into bounded contexts
+- **Visualize your architecture** — auto-generated diagrams of your services and message flows
+- **Version everything** — track how your architecture evolves over time
+- **Use AI to explore & document** — connect AI tools directly to your catalog
+
+## Use AI with Your Catalog
+
+### Skills
+
+Let AI agents document your architecture for you. Install [EventCatalog Skills](https://github.com/event-catalog/skills):
+
+```sh
+npx skills add event-catalog/skills
+```
+
+Skills can generate service documentation, create domain models, and map business flows — all through natural language.
+
+### MCP Server
+
+Connect your catalog to Claude, Cursor, Windsurf, or any MCP-compatible AI tool using the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server). Ask questions about your architecture and get instant answers.
+
+## Automate Your Catalog
+
+Keep your catalog in sync with your architecture using [EventCatalog integrations](https://www.eventcatalog.dev/integrations). Import services, messages, and schemas from sources like AsyncAPI, OpenAPI, Schema Registries, and more — so your documentation is always up to date.
+
+## Learn More
+
+- [Documentation](https://www.eventcatalog.dev/docs/development/getting-started/introduction) — understand how EventCatalog works
+- [Adding Services](https://www.eventcatalog.dev/docs/development/guides/services) — document your first service
+- [Adding Messages](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages) — create events, commands, and queries
+- [Adding Domains](https://www.eventcatalog.dev/docs/development/guides/domains) — organize into bounded contexts
+- [SDK](https://www.eventcatalog.dev/docs/development/sdk) — manage your catalog programmatically
+- [Discord](https://discord.gg/3rjaZMmrAm) — join the community
+
+## Found a problem?
+
+Open an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues).

package/templates/asyncapi/gitignore

@@ -24,4 +24,6 @@ yarn-error.log*
 .eventcatalog-core
 
 .env
-.env-*
+.env-*
+
+exports/*

package/templates/confluent/gitignore

@@ -24,4 +24,6 @@ yarn-error.log*
 .eventcatalog-core
 
 .env
-.env-*
+.env-*
+
+exports/*

package/templates/default/README-template.md

@@ -1 +1,55 @@
 # My Event Catalog
+
+Welcome to your new catalog, powered by [EventCatalog](https://www.eventcatalog.dev) — the open-source documentation tool for event-driven architectures.
+
+## Getting Started
+
+```sh
+npm run dev
+```
+
+Open [http://localhost:3000](http://localhost:3000) to see your catalog.
+
+You can start editing your catalog by adding **domains**, **services**, and **messages** to this project. Each resource is a folder with an `index.md` file containing frontmatter metadata and markdown content.
+
+## What Can You Do?
+
+- **Document services** — define producers and consumers with their schemas
+- **Map events, commands & queries** — capture every message flowing through your system
+- **Organize with domains** — group resources into bounded contexts
+- **Visualize your architecture** — auto-generated diagrams of your services and message flows
+- **Version everything** — track how your architecture evolves over time
+- **Use AI to explore & document** — connect AI tools directly to your catalog
+
+## Use AI with Your Catalog
+
+### Skills
+
+Let AI agents document your architecture for you. Install [EventCatalog Skills](https://github.com/event-catalog/skills):
+
+```sh
+npx skills add event-catalog/skills
+```
+
+Skills can generate service documentation, create domain models, and map business flows — all through natural language.
+
+### MCP Server
+
+Connect your catalog to Claude, Cursor, Windsurf, or any MCP-compatible AI tool using the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server). Ask questions about your architecture and get instant answers.
+
+## Automate Your Catalog
+
+Keep your catalog in sync with your architecture using [EventCatalog integrations](https://www.eventcatalog.dev/integrations). Import services, messages, and schemas from sources like AsyncAPI, OpenAPI, Schema Registries, and more — so your documentation is always up to date.
+
+## Learn More
+
+- [Documentation](https://www.eventcatalog.dev/docs/development/getting-started/introduction) — understand how EventCatalog works
+- [Adding Services](https://www.eventcatalog.dev/docs/development/guides/services) — document your first service
+- [Adding Messages](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages) — create events, commands, and queries
+- [Adding Domains](https://www.eventcatalog.dev/docs/development/guides/domains) — organize into bounded contexts
+- [SDK](https://www.eventcatalog.dev/docs/development/sdk) — manage your catalog programmatically
+- [Discord](https://discord.gg/3rjaZMmrAm) — join the community
+
+## Found a problem?
+
+Open an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues).

package/templates/default/gitignore

@@ -24,4 +24,6 @@ yarn-error.log*
 .eventcatalog-core
 
 .env
-.env-*
+.env-*
+
+exports/*

package/templates/empty/README-template.md

@@ -1 +1,55 @@
 # My Event Catalog
+
+Welcome to your new catalog, powered by [EventCatalog](https://www.eventcatalog.dev) — the open-source documentation tool for event-driven architectures.
+
+## Getting Started
+
+```sh
+npm run dev
+```
+
+Open [http://localhost:3000](http://localhost:3000) to see your catalog.
+
+You can start editing your catalog by adding **domains**, **services**, and **messages** to this project. Each resource is a folder with an `index.md` file containing frontmatter metadata and markdown content.
+
+## What Can You Do?
+
+- **Document services** — define producers and consumers with their schemas
+- **Map events, commands & queries** — capture every message flowing through your system
+- **Organize with domains** — group resources into bounded contexts
+- **Visualize your architecture** — auto-generated diagrams of your services and message flows
+- **Version everything** — track how your architecture evolves over time
+- **Use AI to explore & document** — connect AI tools directly to your catalog
+
+## Use AI with Your Catalog
+
+### Skills
+
+Let AI agents document your architecture for you. Install [EventCatalog Skills](https://github.com/event-catalog/skills):
+
+```sh
+npx skills add event-catalog/skills
+```
+
+Skills can generate service documentation, create domain models, and map business flows — all through natural language.
+
+### MCP Server
+
+Connect your catalog to Claude, Cursor, Windsurf, or any MCP-compatible AI tool using the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server). Ask questions about your architecture and get instant answers.
+
+## Automate Your Catalog
+
+Keep your catalog in sync with your architecture using [EventCatalog integrations](https://www.eventcatalog.dev/integrations). Import services, messages, and schemas from sources like AsyncAPI, OpenAPI, Schema Registries, and more — so your documentation is always up to date.
+
+## Learn More
+
+- [Documentation](https://www.eventcatalog.dev/docs/development/getting-started/introduction) — understand how EventCatalog works
+- [Adding Services](https://www.eventcatalog.dev/docs/development/guides/services) — document your first service
+- [Adding Messages](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages) — create events, commands, and queries
+- [Adding Domains](https://www.eventcatalog.dev/docs/development/guides/domains) — organize into bounded contexts
+- [SDK](https://www.eventcatalog.dev/docs/development/sdk) — manage your catalog programmatically
+- [Discord](https://discord.gg/3rjaZMmrAm) — join the community
+
+## Found a problem?
+
+Open an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues).

package/templates/empty/gitignore

@@ -24,4 +24,6 @@ yarn-error.log*
 .eventcatalog-core
 
 .env
-.env-*
+.env-*
+
+exports/*

package/templates/eventbridge/gitignore

@@ -24,4 +24,6 @@ yarn-error.log*
 .eventcatalog-core
 
 .env
-.env-*
+.env-*
+
+exports/*

package/templates/graphql/README-template.md

@@ -1 +1,55 @@
 # My Event Catalog
+
+Welcome to your new catalog, powered by [EventCatalog](https://www.eventcatalog.dev) — the open-source documentation tool for event-driven architectures.
+
+## Getting Started
+
+```sh
+npm run dev
+```
+
+Open [http://localhost:3000](http://localhost:3000) to see your catalog.
+
+You can start editing your catalog by adding **domains**, **services**, and **messages** to this project. Each resource is a folder with an `index.md` file containing frontmatter metadata and markdown content.
+
+## What Can You Do?
+
+- **Document services** — define producers and consumers with their schemas
+- **Map events, commands & queries** — capture every message flowing through your system
+- **Organize with domains** — group resources into bounded contexts
+- **Visualize your architecture** — auto-generated diagrams of your services and message flows
+- **Version everything** — track how your architecture evolves over time
+- **Use AI to explore & document** — connect AI tools directly to your catalog
+
+## Use AI with Your Catalog
+
+### Skills
+
+Let AI agents document your architecture for you. Install [EventCatalog Skills](https://github.com/event-catalog/skills):
+
+```sh
+npx skills add event-catalog/skills
+```
+
+Skills can generate service documentation, create domain models, and map business flows — all through natural language.
+
+### MCP Server
+
+Connect your catalog to Claude, Cursor, Windsurf, or any MCP-compatible AI tool using the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server). Ask questions about your architecture and get instant answers.
+
+## Automate Your Catalog
+
+Keep your catalog in sync with your architecture using [EventCatalog integrations](https://www.eventcatalog.dev/integrations). Import services, messages, and schemas from sources like AsyncAPI, OpenAPI, Schema Registries, and more — so your documentation is always up to date.
+
+## Learn More
+
+- [Documentation](https://www.eventcatalog.dev/docs/development/getting-started/introduction) — understand how EventCatalog works
+- [Adding Services](https://www.eventcatalog.dev/docs/development/guides/services) — document your first service
+- [Adding Messages](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages) — create events, commands, and queries
+- [Adding Domains](https://www.eventcatalog.dev/docs/development/guides/domains) — organize into bounded contexts
+- [SDK](https://www.eventcatalog.dev/docs/development/sdk) — manage your catalog programmatically
+- [Discord](https://discord.gg/3rjaZMmrAm) — join the community
+
+## Found a problem?
+
+Open an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues).

package/templates/graphql/gitignore

@@ -24,4 +24,6 @@ yarn-error.log*
 .eventcatalog-core
 
 .env
-.env-*
+.env-*
+
+exports/*

package/templates/index.ts

@@ -42,6 +42,7 @@ export const installTemplate = async ({
       start: 'eventcatalog start',
       preview: 'eventcatalog preview',
       generate: 'eventcatalog generate',
+      export: 'eventcatalog export',
       lint: 'eventcatalog-linter',
       test: 'echo "Error: no test specified" && exit 1',
     },

package/templates/openapi/README-template.md

@@ -1 +1,59 @@
 # My Event Catalog
+
+Welcome to your new catalog, powered by [EventCatalog](https://www.eventcatalog.dev) — the open-source documentation tool for event-driven architectures.
+
+## Getting Started
+
+```sh
+npm run dev
+```
+
+Open [http://localhost:3000](http://localhost:3000) to see your catalog.
+
+You can start editing your catalog by adding **domains**, **services**, and **messages** to this project. Each resource is a folder with an `index.md` file containing frontmatter metadata and markdown content.
+
+## What Can You Do?
+
+- **Document services** — define producers and consumers with their schemas
+- **Map events, commands & queries** — capture every message flowing through your system
+- **Organize with domains** — group resources into bounded contexts
+- **Visualize your architecture** — auto-generated diagrams of your services and message flows
+- **Version everything** — track how your architecture evolves over time
+- **Use AI to explore & document** — connect AI tools directly to your catalog
+
+## Use AI with Your Catalog
+
+### Skills
+
+Let AI agents document your architecture for you. Install [EventCatalog Skills](https://github.com/event-catalog/skills):
+
+```sh
+npx skills add event-catalog/skills
+```
+
+Skills can generate service documentation, create domain models, and map business flows — all through natural language.
+
+### MCP Server
+
+Connect your catalog to Claude, Cursor, Windsurf, or any MCP-compatible AI tool using the [EventCatalog MCP Server](https://www.eventcatalog.dev/docs/development/guides/ai/using-mcp-server). Ask questions about your architecture and get instant answers.
+
+## Automate Your Catalog
+
+Keep your catalog in sync with your architecture using [EventCatalog integrations](https://www.eventcatalog.dev/integrations). Import services, messages, and schemas from sources like AsyncAPI, OpenAPI, Confluent Schema Registry, AWS EventBridge, and more — so your documentation is always up to date.
+
+## Automate Your Catalog
+
+Keep your catalog in sync with your architecture using [EventCatalog integrations](https://www.eventcatalog.dev/integrations). Import services, messages, and schemas from sources like AsyncAPI, OpenAPI, Schema Registries, and more — so your documentation is always up to date.
+
+## Learn More
+
+- [Documentation](https://www.eventcatalog.dev/docs/development/getting-started/introduction) — understand how EventCatalog works
+- [Adding Services](https://www.eventcatalog.dev/docs/development/guides/services) — document your first service
+- [Adding Messages](https://www.eventcatalog.dev/docs/development/guides/messages/adding-messages) — create events, commands, and queries
+- [Adding Domains](https://www.eventcatalog.dev/docs/development/guides/domains) — organize into bounded contexts
+- [SDK](https://www.eventcatalog.dev/docs/development/sdk) — manage your catalog programmatically
+- [Discord](https://discord.gg/3rjaZMmrAm) — join the community
+
+## Found a problem?
+
+Open an issue on [GitHub](https://github.com/event-catalog/eventcatalog/issues).

package/templates/openapi/gitignore

@@ -24,4 +24,6 @@ yarn-error.log*
 .eventcatalog-core
 
 .env
-.env-*
+.env-*
+
+exports/*