@eventcatalog/core 5.7.1 → 5.7.4

package/dist/analytics/analytics.cjs

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(analytics_exports);
 var import_os = __toESM(require("os"), 1);
 
 // package.json
-var version = "5.7.1";
+var version = "5.7.4";
 
 // src/constants.ts
 var VERSION = version;

package/dist/analytics/analytics.js

@@ -1,8 +1,8 @@
 import {
   raiseEvent
-} from "../chunk-GRC67WHC.js";
+} from "../chunk-GOIDVIMH.js";
 import "../chunk-CPW6G62V.js";
-import "../chunk-HZ3XZKUT.js";
+import "../chunk-L2PFSX4L.js";
 export {
   raiseEvent
 };

package/dist/analytics/log-build.cjs

@@ -169,7 +169,7 @@ var verifyRequiredFieldsAreInCatalogConfigFile = async (projectDirectory) => {
 var import_os = __toESM(require("os"), 1);
 
 // package.json
-var version = "5.7.1";
+var version = "5.7.4";
 
 // src/constants.ts
 var VERSION = version;

package/dist/analytics/log-build.js

@@ -1,12 +1,12 @@
 import {
   log_build_default
-} from "../chunk-36XVRD36.js";
+} from "../chunk-PLTHZFTW.js";
 import "../chunk-AD7CL772.js";
-import "../chunk-GRC67WHC.js";
+import "../chunk-GOIDVIMH.js";
 import "../chunk-YRZK7HKX.js";
 import "../chunk-CA6WCQ2T.js";
 import "../chunk-CPW6G62V.js";
-import "../chunk-HZ3XZKUT.js";
+import "../chunk-L2PFSX4L.js";
 import "../chunk-4G7FSRPN.js";
 export {
   log_build_default as default

package/dist/{chunk-GRC67WHC.js → chunk-GOIDVIMH.js}

@@ -4,7 +4,7 @@ import {
 } from "./chunk-CPW6G62V.js";
 import {
   VERSION
-} from "./chunk-HZ3XZKUT.js";
+} from "./chunk-L2PFSX4L.js";
 
 // src/analytics/analytics.js
 import os from "os";

package/dist/{chunk-HZ3XZKUT.js → chunk-L2PFSX4L.js}

@@ -1,5 +1,5 @@
 // package.json
-var version = "5.7.1";
+var version = "5.7.4";
 
 // src/constants.ts
 var VERSION = version;

package/dist/{chunk-36XVRD36.js → chunk-PLTHZFTW.js}

@@ -3,7 +3,7 @@ import {
 } from "./chunk-AD7CL772.js";
 import {
   raiseEvent
-} from "./chunk-GRC67WHC.js";
+} from "./chunk-GOIDVIMH.js";
 import {
   countResources,
   hashCatalogContent,

package/dist/{chunk-CPF5WE3R.js → chunk-PXYVJK54.js}

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-HZ3XZKUT.js";
+} from "./chunk-L2PFSX4L.js";
 
 // src/utils/cli-logger.ts
 import pc from "picocolors";

package/dist/{chunk-AXWTR2FV.js → chunk-RUG7AIT5.js}

@@ -1,6 +1,6 @@
 import {
   logger
-} from "./chunk-CPF5WE3R.js";
+} from "./chunk-PXYVJK54.js";
 import {
   cleanup,
   getEventCatalogConfigFile

package/dist/constants.cjs

@@ -25,7 +25,7 @@ __export(constants_exports, {
 module.exports = __toCommonJS(constants_exports);
 
 // package.json
-var version = "5.7.1";
+var version = "5.7.4";
 
 // src/constants.ts
 var VERSION = version;

package/dist/constants.js

@@ -1,6 +1,6 @@
 import {
   VERSION
-} from "./chunk-HZ3XZKUT.js";
+} from "./chunk-L2PFSX4L.js";
 export {
   VERSION
 };

package/dist/docs/development/ask-your-architecture/02-eventcatalog-assistant/01-what-is-eventcatalog-assistant.md

@@ -18,3 +18,11 @@ It is embedded directly into your documentation site, enabling users to quickly
 The assistant integrates with your preferred AI models using the [AI SDK](https://ai-sdk.dev/), giving you full control over which models power the experience.
 
 ![EventCatalog Assistant](./images/example.png)
+
+## Draw with AI in Studio
+
+<AddedIn version="5.7.1" />
+
+On an [EventCatalog Studio](/docs/development/studio/introduction) canvas, the assistant can draw for you. Choose **Draw with AI** and describe what you want to design: the assistant draws it on the canvas, live, using the resources in your catalog. It can also review a design and flag risks with hotspots, or walk you through how something works, step by step.
+
+See [Draw with AI](/docs/development/studio/draw-with-ai).

package/dist/docs/development/ask-your-architecture/02-eventcatalog-assistant/02-configuration.md

@@ -78,6 +78,30 @@ export const configuration = {
 }
 ```
 
+#### Passing options to your provider
+
+<AddedIn version="5.7.1" />
+
+Use `configuration.providerOptions` to pass settings that only your model provider understands. They're passed to the [AI SDK's `providerOptions`](https://ai-sdk.dev/docs/foundations/prompts), keyed by the provider's name.
+
+For example, to set how much effort an Anthropic model puts into its answers:
+
+```js title="eventcatalog.chat.js"
+import { anthropic } from '@ai-sdk/anthropic';
+
+export default async () => {
+    return anthropic('claude-haiku-5-5');
+}
+
+export const configuration = {
+    providerOptions: {
+        anthropic: { effort: 'medium' },
+    },
+}
+```
+
+Lower effort answers faster and costs less, which suits most drawing with [Draw with AI](/docs/development/studio/draw-with-ai). Raise it for harder questions. See your provider's page in the [AI SDK docs](https://ai-sdk.dev/providers/ai-sdk-providers) for the options it accepts.
+
 Once you have configured your model, restart EventCatalog and you can start asking questions about your architecture.
 
 ### Troubleshooting

package/dist/docs/development/studio/01-introduction.md

@@ -31,7 +31,7 @@ With Studio:
 - **You sketch what's new next to what exists.** Add proposed services, messages and data stores, and connect them to the resources they change.
 - **Team collaboration.** Everyone on a canvas sees each other's pointers and edits, and can comment and flag risks.
 - **You record the decision.** Mark a canvas as proposed, accepted or rejected, with a note, so you can see later what was decided and why.
-- **AI agents work with you.** Agents connect through the [MCP server](/docs/development/ask-your-architecture/mcp-server/introduction) and edit the same canvas, using the resources in your catalog.
+- **AI works with you.** Choose [Draw with AI](/docs/development/studio/draw-with-ai) and describe what you want: the assistant draws it on the canvas with the model you configure. Agents such as Claude and Cursor can also connect through the [MCP server](/docs/development/ask-your-architecture/mcp-server/introduction) and edit the same canvas, using the resources in your catalog.
 
 :::info Studio doesn't change your catalog
 A canvas is a design, kept separately from your catalog files. Adding, editing or deleting anything on a canvas never changes your documentation.
@@ -57,4 +57,5 @@ Try [EventCatalog Studio on the web](https://www.eventcatalog.studio/). It runs
 
 - [Create a canvas](/docs/development/studio/create-a-canvas)
 - [Collaborate on a canvas](/docs/development/studio/collaborate-on-a-canvas)
+- [Draw with AI](/docs/development/studio/draw-with-ai)
 - [Connect your agent to a canvas](/docs/development/studio/connect-your-agent)

package/dist/docs/development/studio/04-collaborate-on-a-canvas.md

@@ -46,9 +46,17 @@ A hotspot flags a risk on a node or a spot, such as a single point of failure or
 2. Click the node at risk.
 3. Pick **Critical**, **Warning** or **Info**, and add a short title and, if you want, why it matters.
 
-**Hotspots** at the bottom of the canvas lists every hotspot. At L1 and L2, hotspots inside a domain or system are shown on that domain or system, so zooming out never hides a risk.
+Click a marker to open its hotspot beside it. It shows the title, why it matters, and who flagged it and when. Edit or remove it from its header, or press <kbd>Delete</kbd> to remove it.
 
-![A warning hotspot on the Instalment Plans database](./img/hotspots.png)
+**Hotspots** at the bottom of the canvas lists every hotspot, most severe first, with the node it's on. Click a row, or rest the pointer on it, to go to that hotspot and open it. The list stays open, so you can work through them one by one.
+
+At L1 and L2, hotspots inside a domain or system are shown on that domain or system, so zooming out never hides a risk. Deleting a node deletes its hotspots too.
+
+![The Hotspots list on a Payments canvas, with the critical "Shared database single point of failure" hotspot open beside the Payment Database](./img/hotspot-list.png)
+
+:::tip Let the assistant find risks
+Ask the assistant to review a canvas with [Draw with AI](/docs/development/studio/draw-with-ai#ask-it-to-review-a-design), and it flags what it finds with hotspots.
+:::
 
 ## Add notes and text
 

package/dist/docs/development/studio/05-connect-your-agent.md

@@ -12,6 +12,10 @@ description: Bring Claude, ChatGPT, Cursor or another AI agent onto a canvas to
 
 AI agents can join a canvas and work on it with you, live. An agent can add resources from your catalog, sketch new components, connect them, tidy the layout, comment and change the status.
 
+:::tip No agent to connect?
+[Draw with AI](/docs/development/studio/draw-with-ai) uses the EventCatalog Assistant, built into your catalog, to draw on the canvas with the model you configure.
+:::
+
 Agents join like a person does. Each one has its own pointer and name, and you see what it's doing ("Connecting InstalmentPlanApproved to Notification Service") as it works. Choose **Follow** on the "is working" banner to move your view with it.
 
 ![Claude connecting an event to the Notification Service while two people are on the canvas](./img/studio-collaboration.png)

package/dist/docs/development/studio/07-reference.md

@@ -111,10 +111,15 @@ The bottom of the menu shows the connection status, for example **Connected**.
 
 ### Right-click menus
 
+Items are grouped, with their shortcuts on the right. On a locked canvas, only the items that don't change it are shown.
+
 | On | Items |
 |---|---|
-| A node | Add comment, Add hotspot, Add a note, Edit details, Copy, Duplicate, Delete |
-| The canvas | Add comment, Add hotspot, Add a sticky note, Paste here, Reorder diagram |
+| A node | Edit details · Cut, Copy, Paste, Duplicate · Add comment, Add hotspot, Add note · Delete |
+| A sticky note or text | Edit text · Cut, Copy, Paste, Duplicate · Colour (sticky notes) · Add comment · Delete |
+| The canvas | Paste here · Add sticky note, Add comment, Add hotspot · Reorder diagram |
+
+**Cut** is offered at L3, where nodes can be copied.
 
 ### Statuses
 
@@ -136,8 +141,10 @@ The bottom of the menu shows the connection status, for example **Connected**.
 | Title | Up to 120 characters, for example "Single point of failure" |
 | Description | Optional. Why it matters, and what to do about it |
 
-- A hotspot is on a node, and moves with it, or on a spot on the canvas.
-- The **Hotspots** list shows the most severe first.
+- A hotspot is on a node, and moves with it, or on a spot on the canvas. Deleting a node deletes its hotspots, and undo brings them back.
+- A marker shows the severity's icon, with a count when there's more than one hotspot on it. Click it to open the hotspot beside it.
+- An open hotspot shows its title, description, and who flagged it and when. Edit or remove it from its header, or press <kbd>Delete</kbd> to remove it.
+- The **Hotspots** list at the bottom left has one row per hotspot, most severe first, with the node it's on. Click a row, or rest the pointer on it, to go to that hotspot and open it.
 - At L1 and L2, hotspots inside a domain or system are shown on that domain or system.
 
 ### Studio page
@@ -178,7 +185,7 @@ New components start at version `0.0.1`.
 | People | Actor | Someone who uses it |
 | | Team | Who owns what |
 
-Sticky notes and text are added from the toolbar.
+Sticky notes and text are added from the toolbar. Agents and the [assistant](/docs/development/studio/draw-with-ai) can add them too, and they're always placed clear of other nodes.
 
 ### Catalog resources
 
@@ -221,8 +228,8 @@ When Studio is on, the [EventCatalog MCP server](/docs/development/ask-your-arch
 | `openCanvas` | Shows a canvas in the chat, in clients that support MCP Apps |
 | `listCanvases` | Lists canvases and who is on each one |
 | `createCanvas` | Creates a canvas and returns its link |
-| `getCanvas` | Reads a canvas: its nodes, connections, comments and who is on it |
-| `addToCanvas` | Adds catalog resources or new components, and connects them |
+| `getCanvas` | Reads a canvas: its nodes, connections, hotspots, comments and who is on it |
+| `addToCanvas` | Adds catalog resources, new components, sticky notes and text, and connects them |
 | `updateCanvasNode` | Renames, describes, versions or moves a node |
 | `connectCanvasNodes` | Connects nodes |
 | `removeFromCanvas` | Removes nodes or connections |
@@ -234,6 +241,12 @@ When Studio is on, the [EventCatalog MCP server](/docs/development/ask-your-arch
 
 Every tool takes an optional `agentName`, the name people on the canvas see. It defaults to the name of the client, for example Claude, Claude Code, ChatGPT or Cursor.
 
+`addToCanvas` can bring more than one resource at a time:
+
+- `contents: true` on a catalog domain or system adds it with everything in it: its systems, services, messages and data stores, connected and laid out.
+- `connections` on a catalog service or message adds what it connects to. For a service: `sends`, `receives` and `dataStores`. For a message: `senders` and `receivers`.
+- A node with type `note` is a sticky note, and type `text` is text on the canvas, with an optional `fontSize`.
+
 ### How agents appear
 
 - An agent has its own pointer and name on the canvas.
@@ -244,6 +257,25 @@ Every tool takes an optional `agentName`, the name people on the canvas see. It
 
 When WebMCP is turned on in the **Connect your AI agent** dialog, the open canvas offers agents in the browser these tools: `get_canvas`, `search_catalog`, `add_to_canvas`, `update_node`, `connect_nodes`, `remove_from_canvas`, `layout_canvas`, `set_canvas_status`, `add_comment`, `reply_to_comment`, `resolve_comment` and `show_nodes`.
 
+## Assistant tools {#assistant-tools}
+
+When you [draw with AI](/docs/development/studio/draw-with-ai), the EventCatalog Assistant works on the canvas it was opened on with these tools, using the model in `eventcatalog.chat.js`. They're only offered when Studio is on.
+
+| Tool | What it does |
+|---|---|
+| `getCanvas` | Reads the canvas: its nodes, connections, hotspots and comments |
+| `addToCanvas` | Adds catalog resources, new components, sticky notes and text, like the [MCP tool](#mcp-tools) |
+| `updateCanvasNode` | Renames, describes, versions, moves or resizes the text of a node |
+| `connectCanvasNodes` | Connects nodes |
+| `removeFromCanvas` | Removes nodes or connections |
+| `layoutCanvas` | Lays out the whole canvas, when you ask it to |
+| `addHotspot` | Flags a node or a spot with a critical, warning or info hotspot |
+| `showOnCanvas` | Takes your view to nodes and highlights them |
+| `walkThrough` | Shows a step-by-step walkthrough in the chat, with each step's nodes |
+
+- The assistant appears on the canvas as **EventCatalog AI**, with its own pointer, like other agents. It works about three times as fast as an MCP agent, because you're waiting on it in the chat.
+- After a turn where it added nodes or connections, the canvas is laid out again, with sticky notes and text kept beside what they're about.
+
 ## Keyboard shortcuts {#keyboard-shortcuts}
 
 Press <kbd>?</kbd> on a canvas to see these shortcuts. On Windows and Linux, use <kbd>Ctrl</kbd> instead of <kbd>⌘</kbd>.
@@ -270,6 +302,7 @@ Press <kbd>?</kbd> on a canvas to see these shortcuts. On Windows and Linux, use
 | Select everything | <kbd>⌘</kbd> <kbd>A</kbd> |
 | Select several | <kbd>⇧</kbd> + click |
 | Delete what's selected | <kbd>Delete</kbd> |
+| Remove the open hotspot | <kbd>Delete</kbd> |
 | Duplicate | <kbd>⌘</kbd> <kbd>D</kbd> |
 | Copy / paste | <kbd>⌘</kbd> <kbd>C</kbd> / <kbd>⌘</kbd> <kbd>V</kbd> |
 | Undo / redo | <kbd>⌘</kbd> <kbd>Z</kbd> / <kbd>⌘</kbd> <kbd>⇧</kbd> <kbd>Z</kbd> |

package/dist/docs/development/studio/draw-with-ai.md

@@ -0,0 +1,96 @@
+---
+sidebar_position: 4.5
+keywords:
+- EventCatalog Studio
+- Draw with AI
+- AI architecture diagrams
+- EventCatalog Assistant
+sidebar_label: Draw with AI
+title: Draw with AI
+description: Describe what you want to design, and the assistant draws it on the canvas with the model you configure.
+---
+
+import AddedIn from '@site/src/components/MDX/AddedIn';
+
+<AddedIn version="5.7.1" />
+
+Describe what you want to design, and the [EventCatalog Assistant](/docs/development/ask-your-architecture/eventcatalog-assistant/what-is-eventcatalog-assistant) draws it on the canvas while you watch. It uses the resources in your catalog and the AI model you configure.
+
+![The assistant drawing a buy now, pay later design on a canvas, with its pointer on the canvas and its progress in the chat](./img/draw-with-ai.png)
+
+## Before you start
+
+Draw with AI uses the EventCatalog Assistant, so your catalog needs:
+
+- Studio turned on. It's on in `eventcatalog dev`; see [Run Studio in production](/docs/development/studio/run-studio-in-production) for a deployed catalog.
+- A model configured in `eventcatalog.chat.js`. See [Configure the assistant](/docs/development/ask-your-architecture/eventcatalog-assistant/configuration).
+
+**Draw with AI** only appears on a canvas when the assistant is available.
+
+## Draw on a canvas
+
+1. Open a canvas, or start one from a diagram with **Open in Studio**.
+2. Choose **Draw with AI** at the top right. The assistant opens beside the canvas.
+3. Describe what you want, for example "Map out the Payments domain", and press <kbd>Enter</kbd>.
+
+The assistant reads the canvas, finds what you asked about in your catalog, and draws it with its own pointer, one step at a time. The chat shows what it's doing ("Reading the canvas", "Drawing on the canvas"). Your view follows it while it works; choose **Stop** on the "Following" banner to look around on your own.
+
+When it's finished, the assistant tidies the layout and keeps sticky notes and text beside what they're about.
+
+Everyone on the canvas sees the assistant's pointer and changes, as they see each other's.
+
+## What it draws
+
+- **Resources from your catalog**, with their real names, versions and summaries. A domain or system arrives with everything in it. A service or message can arrive with what it sends, receives and connects to.
+- **New components** for what isn't in your catalog yet, such as a proposed service or event. They start at version `0.0.1`.
+- **Sticky notes and text**, when you ask for them or ask for a review: assumptions, open questions, a title or headings.
+
+Connections between catalog resources come from your catalog, not from the model. If the assistant can't find something you asked for, it says so in its reply.
+
+:::info Your catalog doesn't change
+Like everything on a canvas, what the assistant draws is a design. It never changes your catalog files.
+:::
+
+## Ask it to review a design
+
+Ask the assistant to review a canvas, and it flags what it finds with [hotspots](/docs/development/studio/collaborate-on-a-canvas#flag-a-risk-with-a-hotspot) on the nodes they're about, marked **Critical**, **Warning** or **Info**. It can add sticky notes with suggestions too.
+
+The hotspots it flags are listed under its reply. Click one to go to it on the canvas. Each one says **Flagged by EventCatalog AI**, so your team can tell them apart from their own.
+
+![The assistant's review of the Payments domain, listing six hotspots it flagged on the canvas](./img/draw-with-ai-review.png)
+
+## Ask how something works
+
+Ask "walk me through how checkout works", and the assistant answers with a walkthrough: one step at a time, each with what happens and the nodes involved. Hover or click a step to go to its nodes on the canvas.
+
+When the assistant mentions something on the canvas, its name in the reply links to it. Hover or click it to go there.
+
+![A step-by-step walkthrough in the chat, with the nodes for the current step highlighted on the canvas](./img/draw-with-ai-walkthrough.png)
+
+## Things to ask
+
+When you open the assistant on a canvas, it suggests a few things to ask:
+
+- **Create a new diagram**: the assistant asks what to draw.
+- **Review my architecture, highlight any issues**: it flags problems with hotspots and adds sticky notes with its review.
+- **How could we improve this architecture?**: it flags risks and suggests improvements on sticky notes.
+
+Other things to try:
+
+- "Map out the Payments domain"
+- "Design how we could add buy now, pay later to checkout"
+- "Add a fraud check between checkout and the Payment API"
+- "How could we split the Order Service?"
+- "Walk me through what happens when a payment fails"
+
+After each answer, the assistant suggests follow-up questions based on what's on the canvas.
+
+## Choosing a model
+
+The assistant uses the model in `eventcatalog.chat.js`, so you choose the provider, the model and who pays for it. Your catalog talks to your provider directly.
+
+A small, fast model is enough for most drawing. To trade speed for more careful answers, pass your provider's options with [`configuration.providerOptions`](/docs/development/ask-your-architecture/eventcatalog-assistant/configuration#configuring-eventcatalogchatjs), for example Anthropic's `effort`.
+
+## The assistant and other agents
+
+The assistant draws with the same canvas actions as agents that [connect through MCP](/docs/development/studio/connect-your-agent), such as Claude, Cursor or VS Code, and appears on the canvas the same way. It also has a few tools of its own: flagging hotspots, taking you to nodes, and walkthroughs. See the [reference](/docs/development/studio/reference#assistant-tools).

package/dist/eventcatalog.cjs

@@ -174,7 +174,7 @@ var verifyRequiredFieldsAreInCatalogConfigFile = async (projectDirectory) => {
 var import_picocolors = __toESM(require("picocolors"), 1);
 
 // package.json
-var version = "5.7.1";
+var version = "5.7.4";
 
 // src/constants.ts
 var VERSION = version;

package/dist/eventcatalog.js

@@ -7,12 +7,12 @@ import {
 import "./chunk-CA4U2JP7.js";
 import {
   log_build_default
-} from "./chunk-36XVRD36.js";
+} from "./chunk-PLTHZFTW.js";
 import {
   getLicenseStatus,
   printLicenseStatus
 } from "./chunk-AD7CL772.js";
-import "./chunk-GRC67WHC.js";
+import "./chunk-GOIDVIMH.js";
 import "./chunk-YRZK7HKX.js";
 import "./chunk-CA6WCQ2T.js";
 import "./chunk-CPW6G62V.js";
@@ -39,10 +39,10 @@ import {
 } from "./chunk-NKNOXQ62.js";
 import {
   generate
-} from "./chunk-AXWTR2FV.js";
+} from "./chunk-RUG7AIT5.js";
 import {
   logger
-} from "./chunk-CPF5WE3R.js";
+} from "./chunk-PXYVJK54.js";
 import {
   resolve_catalog_dependencies_default
 } from "./chunk-PD7KTSYN.js";
@@ -79,7 +79,7 @@ import {
 } from "./chunk-LFQJXLHG.js";
 import {
   VERSION
-} from "./chunk-HZ3XZKUT.js";
+} from "./chunk-L2PFSX4L.js";
 import {
   getEventCatalogConfigFile,
   verifyRequiredFieldsAreInCatalogConfigFile

package/dist/generate.cjs

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

package/dist/generate.js

@@ -1,8 +1,8 @@
 import {
   generate
-} from "./chunk-AXWTR2FV.js";
-import "./chunk-CPF5WE3R.js";
-import "./chunk-HZ3XZKUT.js";
+} from "./chunk-RUG7AIT5.js";
+import "./chunk-PXYVJK54.js";
+import "./chunk-L2PFSX4L.js";
 import "./chunk-4G7FSRPN.js";
 export {
   generate

package/dist/utils/cli-logger.cjs

@@ -36,7 +36,7 @@ module.exports = __toCommonJS(cli_logger_exports);
 var import_picocolors = __toESM(require("picocolors"), 1);
 
 // package.json
-var version = "5.7.1";
+var version = "5.7.4";
 
 // src/constants.ts
 var VERSION = version;

package/dist/utils/cli-logger.js

@@ -1,7 +1,7 @@
 import {
   logger
-} from "../chunk-CPF5WE3R.js";
-import "../chunk-HZ3XZKUT.js";
+} from "../chunk-PXYVJK54.js";
+import "../chunk-L2PFSX4L.js";
 export {
   logger
 };