@eventcatalog/core 5.2.0 → 5.4.0

package/dist/docs/development/guides/fitness-functions/06-examples.md

@@ -0,0 +1,354 @@
+---
+sidebar_position: 6
+sidebar_label: Examples
+title: Fitness function examples
+description: Ready-to-use fitness functions for team ownership, shared databases, coupling, circular commands, deprecated messages and business-critical services.
+---
+
+These fitness functions check rules teams commonly agree on. Copy one into a `fitness/` folder in your catalog, change the names and limits to match your architecture, and run `npx eventcatalog fitness check`.
+
+Each one only works with the relationships and metadata your catalog records. A rule about data stores needs `writesTo` on your services, a rule about deprecation needs `deprecated` on your messages, and so on. If a rule passes when you expect it to fail, check that your catalog documents what it reads.
+
+| Example | Checks | Severity |
+|---|---|---|
+| [Every service is owned by a team](#every-service-is-owned-by-a-team) | Services list a team, not only people, in `owners` | `error` |
+| [Each data store has one writer](#each-data-store-has-one-writer) | No data store is written to by more than one service | `warning` |
+| [Services stay loosely coupled](#services-stay-loosely-coupled) | No service receives more than a set number of messages | `warning` |
+| [No circular commands](#no-circular-commands) | Services don't send commands to each other in a loop | `error` |
+| [No deprecated messages](#no-deprecated-messages) | No service sends or receives a deprecated message | `warning` |
+| [Business-critical services are documented](#business-critical-services-are-documented) | Services with a "Business Critical" badge have a repository, owners and a specification | `error` |
+| [Domain boundaries](#domain-boundaries) | A domain's services only use its own data stores | `error` |
+
+## Every service is owned by a team
+
+`owners` can list [teams and users](/docs/development/guides/owners/what-are-teams-and-users). A service owned only by a person loses its owner when that person moves on. This rule checks each owner with `catalog.getTeam`, and fails services that don't have at least one team.
+
+```ts title="fitness/team-ownership.fitness.ts"
+import { defineFitnessFunction } from '@eventcatalog/fitness';
+
+export default defineFitnessFunction({
+  id: 'services-owned-by-teams',
+  name: 'Every service is owned by a team',
+  description: 'People move on. A team keeps owning the service when they do.',
+
+  async run({ catalog }) {
+    const services = await catalog.getServices({ latestOnly: true });
+    const violations = [];
+
+    for (const service of services) {
+      // owners can list teams and users. Keep the ones that are teams.
+      const teams = [];
+      for (const owner of service.owners ?? []) {
+        if (await catalog.getTeam(owner)) teams.push(owner);
+      }
+
+      if (teams.length === 0) {
+        violations.push({
+          message: `${service.name} is not owned by a team`,
+          resources: [{ type: 'service', id: service.id, version: service.version }],
+          suggestion: 'Add the owning team to the owners field',
+        });
+      }
+    }
+
+    return violations;
+  },
+});
+```
+
+```
+✗ Every service is owned by a team  1 violation
+    • Payment Worker is not owned by a team
+      Resources: payment-worker (service)
+      Suggestion: Add the owning team to the owners field
+```
+
+## Each data store has one writer
+
+When several services write to the same [data store](/docs/development/guides/resources/data/introduction), none of them can change its schema without coordinating with the others. This rule groups services by the data stores in their [`writesTo`](/docs/development/guides/resources/data/add-read-write-relationships) and warns about any data store with more than one writer.
+
+```ts title="fitness/single-writer.fitness.ts"
+import { defineFitnessFunction } from '@eventcatalog/fitness';
+
+export default defineFitnessFunction({
+  id: 'single-writer-per-data-store',
+  name: 'Each data store has one writer',
+  description: 'A data store written by several services is a shared database: none of them can change its schema safely.',
+  severity: 'warning',
+
+  async run({ catalog }) {
+    const services = await catalog.getServices({ latestOnly: true });
+
+    // Group the services by the data stores they write to
+    const writers = new Map<string, typeof services>();
+    for (const service of services) {
+      for (const store of service.writesTo ?? []) {
+        writers.set(store.id, [...(writers.get(store.id) ?? []), service]);
+      }
+    }
+
+    return [...writers]
+      .filter(([, services]) => services.length > 1)
+      .map(([storeId, services]) => ({
+        message: `${storeId} is written to by ${services.length} services`,
+        // The data store first, then every service that writes to it
+        resources: [
+          { type: 'container', id: storeId },
+          ...services.map((service) => ({ type: 'service', id: service.id, version: service.version })),
+        ],
+        suggestion: 'Give the data store one owning service, and have the others send it commands or events',
+      }));
+  },
+});
+```
+
+```
+! Each data store has one writer  5 warnings
+    • review-database is written to by 2 services
+      Resources: review-database (container), review-moderation-worker (service), review-api (service)
+      Suggestion: Give the data store one owning service, and have the others send it commands or events
+    • payment-database is written to by 2 services
+      Resources: payment-database (container), payment-worker (service), payment-api (service)
+      Suggestion: Give the data store one owning service, and have the others send it commands or events
+    ...
+```
+
+A worker and an API that share a database can be a deliberate choice. Start this rule as a `warning`, and change it to `error` once the shared data stores you've decided to keep are documented.
+
+## Services stay loosely coupled
+
+A service that receives many messages usually has more than one reason to change. This rule warns when a service receives more messages than a limit you choose.
+
+```ts title="fitness/max-dependencies.fitness.ts"
+import { defineFitnessFunction } from '@eventcatalog/fitness';
+
+const MAX_MESSAGES_RECEIVED = 8;
+
+export default defineFitnessFunction({
+  id: 'max-messages-received',
+  name: `Services receive at most ${MAX_MESSAGES_RECEIVED} messages`,
+  severity: 'warning',
+
+  async run({ catalog }) {
+    const services = await catalog.getServices({ latestOnly: true });
+
+    return services
+      .filter((service) => (service.receives ?? []).length > MAX_MESSAGES_RECEIVED)
+      .map((service) => ({
+        message: `${service.name} receives ${service.receives!.length} messages`,
+        resources: [{ type: 'service', id: service.id, version: service.version }],
+        details: 'A service that reacts to many messages usually has more than one reason to change.',
+        suggestion: 'Look for a group of messages that could move to a service of its own',
+      }));
+  },
+});
+```
+
+To set a different limit for one service, put a copy of the rule in that service's `fitness/` folder and check `resource` instead of every service. See [resource fitness functions](./03-global-and-resource-functions.md#resource-fitness-functions) for an example.
+
+## No circular commands
+
+Events often go back and forth between services, and that's fine: each service reacts to what happened. Commands are different. If service A tells B what to do, and B tells A what to do, the two can't be changed or deployed independently.
+
+This rule builds a graph of which services send commands to which, from what each service `sends` and `receives`, and reports every loop it finds.
+
+```ts title="fitness/no-circular-commands.fitness.ts"
+import { defineFitnessFunction } from '@eventcatalog/fitness';
+
+export default defineFitnessFunction({
+  id: 'no-circular-commands',
+  name: 'Services do not send commands in a circle',
+  description: 'If A commands B and B commands A, neither can be deployed or understood without the other.',
+
+  async run({ catalog }) {
+    const services = await catalog.getServices({ latestOnly: true });
+    const commands = new Set((await catalog.getCommands({ latestOnly: true })).map((command) => command.id));
+
+    // Who sends each command, and who receives it
+    const senders = new Map<string, string[]>();
+    for (const service of services) {
+      for (const message of service.sends ?? []) {
+        if (commands.has(message.id)) senders.set(message.id, [...(senders.get(message.id) ?? []), service.id]);
+      }
+    }
+
+    // An edge from each sender to the service that receives its command
+    const edges = new Map<string, Set<string>>();
+    for (const service of services) {
+      for (const message of service.receives ?? []) {
+        for (const sender of senders.get(message.id) ?? []) {
+          if (sender === service.id) continue;
+          edges.set(sender, (edges.get(sender) ?? new Set()).add(service.id));
+        }
+      }
+    }
+
+    // Depth-first search. Reaching a service that is already on the path means there's a cycle.
+    const cycles = new Map<string, string[]>();
+    const visit = (id: string, path: string[]) => {
+      if (path.includes(id)) {
+        const cycle = path.slice(path.indexOf(id));
+        // Report each cycle once, however it was reached
+        cycles.set([...cycle].sort().join(','), cycle);
+        return;
+      }
+      for (const next of edges.get(id) ?? []) visit(next, [...path, id]);
+    };
+    for (const id of edges.keys()) visit(id, []);
+
+    return [...cycles.values()].map((cycle) => ({
+      message: `Commands go round in a circle: ${[...cycle, cycle[0]].join(' → ')}`,
+      resources: cycle.map((id) => ({ type: 'service', id })),
+      suggestion: 'Replace one of the commands with an event, so one service reacts instead of being told',
+    }));
+  },
+});
+```
+
+```
+✗ Services do not send commands in a circle  1 violation
+    • Commands go round in a circle: order-service → checkout-orchestrator → order-service
+      Resources: order-service (service), checkout-orchestrator (service)
+      Suggestion: Replace one of the commands with an event, so one service reacts instead of being told
+```
+
+To check for loops through events and queries too, remove the `commands.has(...)` check. Expect more results: in an event-driven architecture, many of those loops are intended.
+
+## No deprecated messages
+
+When you [deprecate a message](/docs/development/guides/resources/messages/versioning-and-lifecycle/deprecate-messages), the services still using it need to move off it. This rule finds every service that still sends or receives a deprecated event, command or query, and includes the deprecation message from the frontmatter in the result.
+
+```ts title="fitness/no-deprecated-messages.fitness.ts"
+import { defineFitnessFunction } from '@eventcatalog/fitness';
+
+export default defineFitnessFunction({
+  id: 'no-deprecated-messages',
+  name: 'Services do not use deprecated messages',
+  severity: 'warning',
+
+  async run({ catalog }) {
+    // Every deprecated event, command and query, by id
+    const messages = [
+      ...(await catalog.getEvents({ latestOnly: true })).map((message) => ({ ...message, type: 'event' })),
+      ...(await catalog.getCommands({ latestOnly: true })).map((message) => ({ ...message, type: 'command' })),
+      ...(await catalog.getQueries({ latestOnly: true })).map((message) => ({ ...message, type: 'query' })),
+    ];
+    const deprecated = new Map(messages.filter((message) => message.deprecated).map((message) => [message.id, message]));
+
+    const services = await catalog.getServices({ latestOnly: true });
+    const violations = [];
+
+    for (const service of services) {
+      for (const pointer of [...(service.sends ?? []), ...(service.receives ?? [])]) {
+        const message = deprecated.get(pointer.id);
+        if (!message) continue;
+
+        violations.push({
+          message: `${service.name} still uses ${message.name}, which is deprecated`,
+          resources: [
+            { type: 'service', id: service.id, version: service.version },
+            { type: message.type, id: message.id, version: message.version },
+          ],
+          // Use the deprecation message from the frontmatter when there is one
+          details: typeof message.deprecated === 'object' ? message.deprecated.message : undefined,
+        });
+      }
+    }
+
+    return violations;
+  },
+});
+```
+
+```
+! Services do not use deprecated messages  1 warning
+    • Order Service still uses Order Amended, which is deprecated
+      Resources: order-service (service), order-amended (event)
+      Use OrderUpdated instead
+```
+
+## Business-critical services are documented
+
+Some services need more documentation than others. This rule finds services marked as business-critical with a badge, and checks each one has a repository, owners and an API specification.
+
+```ts title="fitness/critical-services.fitness.ts"
+import { defineFitnessFunction } from '@eventcatalog/fitness';
+
+export default defineFitnessFunction({
+  id: 'critical-services-documented',
+  name: 'Business-critical services are fully documented',
+
+  async run({ catalog }) {
+    const services = await catalog.getServices({ latestOnly: true });
+
+    // Services are marked as critical with a badge in their frontmatter
+    const critical = services.filter((service) =>
+      service.badges?.some((badge) => badge.content === 'Business Critical')
+    );
+
+    const violations = [];
+    for (const service of critical) {
+      const resources = [{ type: 'service', id: service.id, version: service.version }];
+      if (!service.repository?.url) {
+        violations.push({ message: `${service.name} has no repository`, resources });
+      }
+      if (!service.owners?.length) {
+        violations.push({ message: `${service.name} has no owners`, resources });
+      }
+      if (!service.specifications) {
+        violations.push({ message: `${service.name} has no API specification`, resources });
+      }
+    }
+    return violations;
+  },
+});
+```
+
+The badge is one way to mark a service. You can use any frontmatter your catalog agrees on, for example a custom `x-tier: critical` property, and check `service['x-tier'] === 'critical'` instead.
+
+## Domain boundaries
+
+A domain's services should only use the domain's own data stores. This rule lives in the domain's folder, so it's given the domain as `resource`, and the domain team owns it. The full example is on [Global and resource fitness functions](./03-global-and-resource-functions.md#resource-fitness-functions).
+
+## Share code between fitness functions
+
+Only files ending in `.fitness.ts` are run, so you can keep shared code in other files in a `fitness/` folder and import it. Type the catalog with `ReadOnlyCatalog`:
+
+```ts title="fitness/helpers.ts"
+import type { ReadOnlyCatalog } from '@eventcatalog/fitness';
+
+/** The latest version of every event, command and query, with its type */
+export const getMessages = async (catalog: ReadOnlyCatalog) => [
+  ...(await catalog.getEvents({ latestOnly: true })).map((message) => ({ ...message, type: 'event' as const })),
+  ...(await catalog.getCommands({ latestOnly: true })).map((message) => ({ ...message, type: 'command' as const })),
+  ...(await catalog.getQueries({ latestOnly: true })).map((message) => ({ ...message, type: 'query' as const })),
+];
+```
+
+```ts title="fitness/message-summaries.fitness.ts"
+import { defineFitnessFunction } from '@eventcatalog/fitness';
+import { getMessages } from './helpers';
+
+export default defineFitnessFunction({
+  id: 'message-summaries',
+  name: 'Every message has a summary',
+  severity: 'warning',
+
+  async run({ catalog }) {
+    const messages = await getMessages(catalog);
+
+    return messages
+      .filter((message) => !message.summary?.trim())
+      .map((message) => ({
+        message: `${message.name} has no summary`,
+        resources: [{ type: message.type, id: message.id, version: message.version }],
+      }));
+  },
+});
+```
+
+## Related
+
+- [Create a fitness function](./02-create-fitness-function.md)
+- [API reference](./05-api-reference.md): everything `run` is given and can return
+- [Run in CI](./04-run-in-ci.md)

package/dist/docs/development/guides/fitness-functions/_category_.json

@@ -0,0 +1,11 @@
+{
+  "label": "Fitness functions",
+  "position": 7,
+  "collapsible": true,
+  "collapsed": true,
+  "link": {
+    "type": "generated-index",
+    "slug": "/fitness-functions",
+    "description": "Write your architecture rules as TypeScript functions, run them against your catalog locally or in CI, and see which resources break them."
+  }
+}

package/dist/docs/development/guides/owners/05-teams-reference.md

@@ -78,18 +78,6 @@ email: payments@example.com
 ---
 ```
 
-### `hidden` {#hidden}
-
-- Type: `boolean`
-
-Hide the team from generated lists.
-
-```md title="Example"
----
-hidden: true
----
-```
-
 ### `slackDirectMessageUrl` {#slackDirectMessageUrl}
 
 - Type: `string`

package/dist/docs/development/guides/owners/06-users-reference.md

@@ -90,18 +90,6 @@ email: david@example.com
 ---
 ```
 
-### `hidden` {#hidden}
-
-- Type: `boolean`
-
-Hide the user from generated lists.
-
-```md title="Example"
----
-hidden: true
----
-```
-
 ### `slackDirectMessageUrl` {#slackDirectMessageUrl}
 
 - Type: `string`

package/dist/docs/development/upgrading/v5.md

@@ -328,7 +328,7 @@ Read more about the [service Resources page](/docs/development/guides/resources/
 
 The MCP server has a new `showResource` tool. With `view: "architecture"` it returns a resource's diagram, built the same way as its Diagram page. With `view: "schema"` it shows a message's schema. In MCP clients that support MCP Apps (for example Claude, ChatGPT and VS Code) these open as interactive views. Other clients get Mermaid or the schema code.
 
-Every MCP tool now has a title and is read-only, versions are optional, and hidden resources are not listed. Read more in [interactive diagrams and schemas](/docs/development/ask-your-architecture/mcp-server/getting-started#interactive-diagrams-and-schemas).
+Every MCP tool now has a title and is read-only, and versions are optional. Read more in [interactive diagrams and schemas](/docs/development/ask-your-architecture/mcp-server/getting-started#interactive-diagrams-and-schemas).
 
 ### Settings > MCP lists domain MCP servers
 

package/dist/eventcatalog.cjs

@@ -174,7 +174,7 @@ var verifyRequiredFieldsAreInCatalogConfigFile = async (projectDirectory) => {
 var import_picocolors = __toESM(require("picocolors"), 1);
 
 // package.json
-var version = "5.2.0";
+var version = "5.4.0";
 
 // src/constants.ts
 var VERSION = version;
@@ -377,6 +377,14 @@ var CUSTOM_ROUTE_PATTERNS = {
 };
 var DEFAULT_IGNORES = ["**/versioned/**", "**/dist/**", "**/node_modules/**"];
 var CUSTOM_ROUTE_IGNORES = [...DEFAULT_IGNORES, "pages/**/_*/**", "pages/**/_*"];
+async function countFitnessFunctions(projectDir) {
+  try {
+    const { discoverFitnessFiles } = await import("@eventcatalog/fitness");
+    return discoverFitnessFiles(projectDir).files.length;
+  } catch {
+    return void 0;
+  }
+}
 async function countResources(projectDir) {
   const counts = {};
   for (const [type, patterns] of Object.entries({ ...RESOURCE_PATTERNS, ...CUSTOM_ROUTE_PATTERNS })) {
@@ -390,6 +398,8 @@ async function countResources(projectDir) {
     }
     counts[type] = total;
   }
+  const fitnessFunctions = await countFitnessFunctions(projectDir);
+  if (fitnessFunctions !== void 0) counts.fitnessFunctions = fitnessFunctions;
   return counts;
 }
 async function hashCatalogContent(projectDir) {
@@ -1714,7 +1724,7 @@ var deriveRecordFromPath = async ({
   const segments = normalizedRelativePath.split("/").filter(Boolean);
   const fileName = segments[segments.length - 1] || "";
   const fileNameWithoutExtension = removeExtension(fileName);
-  if (data.hidden === true || data.draft) {
+  if (data.draft) {
     return null;
   }
   if (segments[0] === "docs") {
@@ -3622,6 +3632,20 @@ program.command("generate [siteDir]").description("Start the generator scripts."
   }
   await generate(dir);
 });
+var fitness = program.command("fitness").description("Run the architecture fitness functions in your catalog.");
+fitness.command("check").description("Run every *.fitness.ts function in the catalog, print the results and write them to a JSON report.").option("-o, --output <path>", "Where to write the report, relative to the catalog", ".eventcatalog/fitness/results.json").option("--format <format>", "Output format: text or json", "text").action(async (commandOptions) => {
+  if (import_fs.default.existsSync(import_node_path23.default.join(dir, ".env"))) {
+    import_dotenv.default.config({ path: import_node_path23.default.join(dir, ".env") });
+  }
+  const { runFitnessCheck } = await import("@eventcatalog/fitness");
+  process.exitCode = await runFitnessCheck({
+    dir,
+    output: commandOptions.output,
+    format: commandOptions.format,
+    color: Boolean(process.stdout.isTTY) && !process.env.NO_COLOR
+  });
+  await new Promise((resolve2) => process.stdout.write("", () => resolve2()));
+});
 var reportFederationProgress = (event, verbose = false) => {
   switch (event.type) {
     case "configured":

package/dist/eventcatalog.js

@@ -1,36 +1,34 @@
-import {
-  stopChildWithParent
-} from "./chunk-S5GWAUG5.js";
 import {
   runMigrations
 } from "./chunk-XUAF2H54.js";
 import "./chunk-CA4U2JP7.js";
+import {
+  stopChildWithParent
+} from "./chunk-S5GWAUG5.js";
 import {
   log_build_default
-} from "./chunk-RNYFUWJI.js";
+} from "./chunk-EPDVXHC7.js";
 import {
   getLicenseStatus,
   printLicenseStatus
 } from "./chunk-AD7CL772.js";
-import "./chunk-66OL4B7U.js";
-import "./chunk-ZAZHAVKB.js";
+import "./chunk-YRZK7HKX.js";
 import "./chunk-CA6WCQ2T.js";
-import "./chunk-CPW6G62V.js";
 import {
   FederationConflictError,
   FederationDiagnosticError,
   federateCatalog
-} from "./chunk-QJ7KKN2D.js";
+} from "./chunk-OX6TSVHY.js";
 import "./chunk-WRNH5C3U.js";
 import "./chunk-5EPNFDT5.js";
-import "./chunk-A2RZR3U4.js";
-import "./chunk-SDZQJTJW.js";
+import "./chunk-6K7XZAYI.js";
 import "./chunk-352FGP6W.js";
 import "./chunk-R7Z5ALYI.js";
 import {
   getFederationDiagnosticCounts,
   getVisibleFederationDiagnostics
 } from "./chunk-JJPB6EOZ.js";
+import "./chunk-SDZQJTJW.js";
 import {
   getProjectOutDir,
   isAuthEnabled,
@@ -39,16 +37,16 @@ import {
 } from "./chunk-NKNOXQ62.js";
 import {
   generate
-} from "./chunk-NBYKF4Z4.js";
+} from "./chunk-TERJXCLK.js";
 import {
   logger
-} from "./chunk-XI5HQWM2.js";
+} from "./chunk-O2K4VPDO.js";
 import {
   resolve_catalog_dependencies_default
 } from "./chunk-PD7KTSYN.js";
 import {
   buildSearchIndex
-} from "./chunk-DJCOJ77J.js";
+} from "./chunk-7RJN4FNG.js";
 import {
   getEventCatalogUpdateMessage,
   resolveInstalledCoreVersion
@@ -56,6 +54,8 @@ import {
 import {
   watch
 } from "./chunk-U63GDPPY.js";
+import "./chunk-PAS36QHK.js";
+import "./chunk-CPW6G62V.js";
 import {
   hasCustomExports,
   isCatalogAuthEnabled,
@@ -79,7 +79,7 @@ import {
 } from "./chunk-LFQJXLHG.js";
 import {
   VERSION
-} from "./chunk-N2LLD5TR.js";
+} from "./chunk-OT2U5OES.js";
 import {
   getEventCatalogConfigFile,
   verifyRequiredFieldsAreInCatalogConfigFile
@@ -1191,6 +1191,20 @@ program.command("generate [siteDir]").description("Start the generator scripts."
   }
   await generate(dir);
 });
+var fitness = program.command("fitness").description("Run the architecture fitness functions in your catalog.");
+fitness.command("check").description("Run every *.fitness.ts function in the catalog, print the results and write them to a JSON report.").option("-o, --output <path>", "Where to write the report, relative to the catalog", ".eventcatalog/fitness/results.json").option("--format <format>", "Output format: text or json", "text").action(async (commandOptions) => {
+  if (fs3.existsSync(path2.join(dir, ".env"))) {
+    dotenv.config({ path: path2.join(dir, ".env") });
+  }
+  const { runFitnessCheck } = await import("@eventcatalog/fitness");
+  process.exitCode = await runFitnessCheck({
+    dir,
+    output: commandOptions.output,
+    format: commandOptions.format,
+    color: Boolean(process.stdout.isTTY) && !process.env.NO_COLOR
+  });
+  await new Promise((resolve) => process.stdout.write("", () => resolve()));
+});
 var reportFederationProgress = (event, verbose = false) => {
   switch (event.type) {
     case "configured":

package/dist/federation/federate.js

@@ -2,14 +2,14 @@ import {
   FederationConflictError,
   FederationDiagnosticError,
   federateCatalog
-} from "../chunk-QJ7KKN2D.js";
+} from "../chunk-OX6TSVHY.js";
 import "../chunk-WRNH5C3U.js";
 import "../chunk-5EPNFDT5.js";
-import "../chunk-A2RZR3U4.js";
-import "../chunk-SDZQJTJW.js";
+import "../chunk-6K7XZAYI.js";
 import "../chunk-352FGP6W.js";
 import "../chunk-R7Z5ALYI.js";
 import "../chunk-JJPB6EOZ.js";
+import "../chunk-SDZQJTJW.js";
 import "../chunk-4G7FSRPN.js";
 export {
   FederationConflictError,

package/dist/federation/source-provider.js

@@ -1,8 +1,8 @@
 import {
   createFederationSourceProvider
-} from "../chunk-A2RZR3U4.js";
-import "../chunk-SDZQJTJW.js";
+} from "../chunk-6K7XZAYI.js";
 import "../chunk-352FGP6W.js";
+import "../chunk-SDZQJTJW.js";
 export {
   createFederationSourceProvider
 };

package/dist/generate.cjs

@@ -105,7 +105,7 @@ var getEventCatalogConfigFile = async (projectDirectory) => {
 var import_picocolors = __toESM(require("picocolors"), 1);
 
 // package.json
-var version = "5.2.0";
+var version = "5.4.0";
 
 // src/constants.ts
 var VERSION = version;

package/dist/generate.js

@@ -1,8 +1,8 @@
 import {
   generate
-} from "./chunk-NBYKF4Z4.js";
-import "./chunk-XI5HQWM2.js";
-import "./chunk-N2LLD5TR.js";
+} from "./chunk-TERJXCLK.js";
+import "./chunk-O2K4VPDO.js";
+import "./chunk-OT2U5OES.js";
 import "./chunk-4G7FSRPN.js";
 export {
   generate

package/dist/runtime-dependencies/@eventcatalog__fitness.mjs

@@ -0,0 +1,3 @@
+export * from "@eventcatalog/fitness";
+import * as dependency from "@eventcatalog/fitness";
+export default dependency.default;

package/dist/runtime-dependencies/@modelcontextprotocol__client.mjs

@@ -0,0 +1,3 @@
+export * from "@modelcontextprotocol/client";
+import * as dependency from "@modelcontextprotocol/client";
+export default dependency.default;

package/dist/runtime-dependencies/@modelcontextprotocol__server.mjs

@@ -0,0 +1,3 @@
+export * from "@modelcontextprotocol/server";
+import * as dependency from "@modelcontextprotocol/server";
+export default dependency.default;