@mastra/deployer 1.0.0-beta.2 → 1.0.0-beta.21

package/dist/deploy/log.d.ts

@@ -1,4 +1,4 @@
-import { Transform } from 'stream';
+import { Transform } from 'node:stream';
 import type { IMastraLogger } from '@mastra/core/logger';
 export declare const createPinoStream: (logger: IMastraLogger) => Transform;
 export declare function createChildProcessLogger({ logger, root }: {

package/dist/deploy/log.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"log.d.ts","sourceRoot":"","sources":["../../src/deploy/log.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,SAAS,EAAE,MAAM,QAAQ,CAAC;AACnC,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AAEzD,eAAO,MAAM,gBAAgB,GAAI,QAAQ,aAAa,cAgBrD,CAAC;AAEF,wBAAgB,wBAAwB,CAAC,EAAE,MAAM,EAAE,IAAI,EAAE,EAAE;IAAE,MAAM,EAAE,aAAa,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,IAElF,oBAAoB;IAAE,GAAG,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,EAAE,CAAC;IAAC,GAAG,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAA;CAAE,sBAoC/F"}
+{"version":3,"file":"log.d.ts","sourceRoot":"","sources":["../../src/deploy/log.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,SAAS,EAAE,MAAM,aAAa,CAAC;AACxC,OAAO,KAAK,EAAE,aAAa,EAAE,MAAM,qBAAqB,CAAC;AAEzD,eAAO,MAAM,gBAAgB,GAAI,QAAQ,aAAa,cAgBrD,CAAC;AAEF,wBAAgB,wBAAwB,CAAC,EAAE,MAAM,EAAE,IAAI,EAAE,EAAE;IAAE,MAAM,EAAE,aAAa,CAAC;IAAC,IAAI,EAAE,MAAM,CAAA;CAAE,IAElF,oBAAoB;IAAE,GAAG,EAAE,MAAM,CAAC;IAAC,IAAI,EAAE,MAAM,EAAE,CAAC;IAAC,GAAG,EAAE,MAAM,CAAC,MAAM,EAAE,MAAM,CAAC,CAAA;CAAE,sBAoC/F"}

package/dist/docs/README.md

@@ -0,0 +1,32 @@
+# @mastra/deployer Documentation
+
+> Embedded documentation for coding agents
+
+## Quick Start
+
+```bash
+# Read the skill overview
+cat docs/SKILL.md
+
+# Get the source map
+cat docs/SOURCE_MAP.json
+
+# Read topic documentation
+cat docs/<topic>/01-overview.md
+```
+
+## Structure
+
+```
+docs/
+├── SKILL.md           # Entry point
+├── README.md          # This file
+├── SOURCE_MAP.json    # Export index
+├── deployer/ (1 files)
+├── deployment/ (6 files)
+```
+
+## Version
+
+Package: @mastra/deployer
+Version: 1.0.0-beta.21

package/dist/docs/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: mastra-deployer-docs
+description: Documentation for @mastra/deployer. Includes links to type definitions and readable implementation code in dist/.
+---
+
+# @mastra/deployer Documentation
+
+> **Version**: 1.0.0-beta.21
+> **Package**: @mastra/deployer
+
+## Quick Navigation
+
+Use SOURCE_MAP.json to find any export:
+
+```bash
+cat docs/SOURCE_MAP.json
+```
+
+Each export maps to:
+- **types**: `.d.ts` file with JSDoc and API signatures
+- **implementation**: `.js` chunk file with readable source
+- **docs**: Conceptual documentation in `docs/`
+
+## Top Exports
+
+  - Deps: dist/index.d.ts
+  - FileService: dist/index.d.ts
+  - createChildProcessLogger: dist/index.d.ts
+  - createPinoStream: dist/index.d.ts
+
+See SOURCE_MAP.json for the complete list.
+
+## Available Topics
+
+- [Deployer](deployer/) - 1 file(s)
+- [Deployment](deployment/) - 6 file(s)

package/dist/docs/SOURCE_MAP.json

@@ -0,0 +1,27 @@
+{
+  "version": "1.0.0-beta.21",
+  "package": "@mastra/deployer",
+  "exports": {
+    "Deps": {
+      "types": "dist/index.d.ts",
+      "implementation": "dist/chunk-DPDWM7HQ.js",
+      "line": 60
+    },
+    "FileService": {
+      "types": "dist/index.d.ts",
+      "implementation": "dist/chunk-DPDWM7HQ.js",
+      "line": 337
+    },
+    "createChildProcessLogger": {
+      "types": "dist/index.d.ts",
+      "implementation": "dist/chunk-DPDWM7HQ.js",
+      "line": 24
+    },
+    "createPinoStream": {
+      "types": "dist/index.d.ts",
+      "implementation": "dist/chunk-DPDWM7HQ.js",
+      "line": 12
+    }
+  },
+  "modules": {}
+}

package/dist/docs/deployer/01-reference.md

@@ -0,0 +1,93 @@
+# Deployer API Reference
+
+> API reference for deployer - 1 entries
+
+
+---
+
+## Reference: Deployer
+
+> Documentation for the Deployer abstract class, which handles packaging and deployment of Mastra applications.
+
+The Deployer handles the deployment of standalone Mastra applications by packaging code, managing environment files, and serving applications using the Hono framework. Concrete implementations must define the deploy method for specific deployment targets.
+
+## Usage Example
+
+```typescript
+import { Deployer } from "@mastra/deployer";
+
+// Create a custom deployer by extending the abstract Deployer class
+class CustomDeployer extends Deployer {
+  constructor() {
+    super({ name: "custom-deployer" });
+  }
+
+  // Implement the abstract deploy method
+  async deploy(outputDirectory: string): Promise<void> {
+    // Prepare the output directory
+    await this.prepare(outputDirectory);
+
+    // Bundle the application
+    await this._bundle("server.ts", "mastra.ts", outputDirectory);
+
+    // Custom deployment logic
+  }
+}
+```
+
+## Parameters
+
+### Constructor Parameters
+
+### deploy Parameters
+
+## Methods
+
+## Inherited Methods from Bundler
+
+The Deployer class inherits the following key methods from the Bundler class:
+
+## Core Concepts
+
+### Deployment Lifecycle
+
+The Deployer abstract class implements a structured deployment lifecycle:
+
+1. **Initialization**: The deployer is initialized with a name and creates a Deps instance for dependency management.
+2. **Environment Setup**: The `getEnvFiles` method identifies environment files (.env.production, .env) to be used during deployment.
+3. **Preparation**: The `prepare` method (inherited from Bundler) cleans the output directory and creates necessary subdirectories.
+4. **Bundling**: The `_bundle` method (inherited from Bundler) packages the application code and its dependencies.
+5. **Deployment**: The abstract `deploy` method is implemented by subclasses to handle the actual deployment process.
+
+### Environment File Management
+
+The Deployer class includes built-in support for environment file management through the `getEnvFiles` method. This method:
+
+- Looks for environment files in a predefined order (.env.production, .env)
+- Uses the FileService to find the first existing file
+- Returns an array of found environment files
+- Returns an empty array if no environment files are found
+
+```typescript
+getEnvFiles(): Promise<string[]> {
+  const possibleFiles = ['.env.production', '.env.local', '.env'];
+
+  try {
+    const fileService = new FileService();
+    const envFile = fileService.getFirstExistingFile(possibleFiles);
+
+    return Promise.resolve([envFile]);
+  } catch {}
+
+  return Promise.resolve([]);
+}
+```
+
+### Bundling and Deployment Relationship
+
+The Deployer class extends the Bundler class, establishing a clear relationship between bundling and deployment:
+
+1. **Bundling as a Prerequisite**: Bundling is a prerequisite step for deployment, where the application code is packaged into a deployable format.
+2. **Shared Infrastructure**: Both bundling and deployment share common infrastructure like dependency management and file system operations.
+3. **Specialized Deployment Logic**: While bundling focuses on code packaging, deployment adds environment-specific logic for deploying the bundled code.
+4. **Extensibility**: The abstract `deploy` method allows for creating specialized deployers for different target environments.

package/dist/docs/deployment/01-overview.md

@@ -0,0 +1,60 @@
+> Learn about different deployment options for your Mastra applications
+
+# Deployment Overview
+
+Mastra applications can be deployed to any Node.js-compatible environment. You can deploy a Mastra server, integrate with an existing web framework, deploy to cloud providers, or use Mastra Cloud for managed hosting.
+
+## Runtime support
+
+Mastra can run against any of these runtime environments:
+
+- Node.js `v22.13.0` or later
+- Bun
+- Deno
+- Cloudflare
+
+## Deployment Options
+
+### Mastra Server
+
+Mastra provides a [server](https://mastra.ai/docs/v1/server/mastra-server) powered by Hono that can be deployed independently. Use the `mastra build` command to build your application and deploy the output to your preferred VM, container, or PaaS platform.
+
+Visit the [Mastra server deployment guide](https://mastra.ai/docs/v1/deployment/mastra-server).
+
+### Monorepo
+
+Deploy a Mastra server as part of a monorepo setup, following the same approach as standalone deployment.
+
+Read about [monorepo deployment](https://mastra.ai/docs/v1/deployment/monorepo).
+
+### Cloud Providers
+
+Mastra applications can be deployed to cloud providers and serverless platforms. Mastra includes optional built-in deployers for Vercel, Netlify, and Cloudflare to automate the build and deployment process.
+
+- [Amazon EC2](https://mastra.ai/guides/v1/deployment/amazon-ec2)
+- [AWS Lambda](https://mastra.ai/guides/v1/deployment/aws-lambda)
+- [Azure App Services](https://mastra.ai/guides/v1/deployment/azure-app-services)
+- [Cloudflare](https://mastra.ai/guides/v1/deployment/cloudflare-deployer)
+- [Digital Ocean](https://mastra.ai/guides/v1/deployment/digital-ocean)
+- [Netlify](https://mastra.ai/guides/v1/deployment/netlify-deployer)
+- [Vercel](https://mastra.ai/guides/v1/deployment/vercel-deployer)
+
+### Web Framework
+
+When Mastra is integrated with a web framework, it deploys alongside your application using the framework's standard deployment process. The guides below cover framework-specific configuration requirements for deployment:
+
+- [With Next.js on Vercel](https://mastra.ai/docs/v1/deployment/web-framework#with-nextjs-on-vercel)
+- [With Astro on Vercel](https://mastra.ai/docs/v1/deployment/web-framework#with-astro-on-vercel)
+- [With Astro on Netlify](https://mastra.ai/docs/v1/deployment/web-framework#with-astro-on-netlify)
+
+### Mastra Cloud
+
+We're building Mastra Cloud to be the easiest place to deploy and observe your Mastra agents. It's currently in beta.
+
+Learn more in the [Mastra Cloud docs](https://mastra.ai/docs/v1/mastra-cloud/overview).
+
+## Workflow Runners
+
+Mastra workflows run using the built-in execution engine by default. For production workloads requiring managed infrastructure, workflows can also be deployed to specialized platforms like [Inngest](https://www.inngest.com) that provide step memoization, automatic retries, and real-time monitoring.
+
+Visit the [Workflow Runners guide](https://mastra.ai/docs/v1/deployment/workflow-runners) for execution options and the [Inngest deployment guide](https://mastra.ai/guides/v1/deployment/inngest) for setup instructions.

package/dist/docs/deployment/02-mastra-server.md

@@ -0,0 +1,70 @@
+> Learn how to build a Mastra server with build settings and deployment options.
+
+# Deploy a Mastra Server
+
+Mastra runs as a standard Node.js server and can be deployed across a wide range of environments.
+
+## Default project structure
+
+The [getting started guide](https://mastra.ai/guides/v1/getting-started/quickstart) scaffolds a project with sensible defaults to help you begin quickly. By default, the CLI organizes application files under the `src/mastra/` directory, resulting in a structure similar to the following:
+
+```
+src/
+└── mastra/
+    ├── agents/
+    ├── tools/
+    ├── workflows/
+    └── index.ts
+package.json
+tsconfig.json
+```
+
+## Building
+
+The `mastra build` command starts the build process:
+
+```bash
+mastra build
+```
+
+### Customizing the input directory
+
+If your Mastra files are located elsewhere, use the `--dir` flag to specify the custom location. The `--dir` flag tells Mastra where to find your entry point file (`index.ts` or `index.js`) and related directories.
+
+```bash
+mastra build --dir ./my-project/mastra
+```
+
+## Build process
+
+The build process follows these steps:
+
+1. **Locates entry file**: Finds `index.ts` or `index.js` in your specified directory (default: `src/mastra/`).
+2. **Creates build directory**: Generates a `.mastra/` directory containing:
+   - **`.build`**: Contains dependency analysis, bundled dependencies, and build configuration files.
+   - **`output`**: Contains the production-ready application bundle with `index.mjs` and project-specific files.
+3. **Copies static assets**: Copies the `public/` folder contents to the `output` directory for serving static files.
+4. **Bundles code**: Uses Rollup with tree shaking and source maps for optimization.
+5. **Generates server**: Creates a [Hono](https://hono.dev) HTTP server ready for deployment.
+
+### Build output structure
+
+After building, Mastra creates a `.mastra/` directory with the following structure:
+
+```
+.mastra/
+├── .build/
+└── output/
+```
+
+### `public` folder
+
+If a `public` folder exists in `src/mastra`, its contents are copied into the `.build/output` directory during the build process.
+
+## Running the Server
+
+Start the HTTP server:
+
+```bash
+node .mastra/output/index.mjs
+```

package/dist/docs/deployment/03-monorepo.md

@@ -0,0 +1,70 @@
+> Learn how to deploy Mastra applications that are part of a monorepo setup
+
+# Deploy in a Monorepo
+
+Deploying Mastra in a monorepo follows the same approach as deploying a standalone application. While some [Cloud](https://mastra.ai/guides/v1/deployment) or [Serverless Platform](https://mastra.ai/guides/v1/deployment) providers may introduce extra requirements, the core setup is the same.
+
+## Supported monorepos
+
+Mastra works with:
+
+- npm workspaces
+- pnpm workspaces
+- Yarn workspaces
+- Turborepo
+
+Known limitations:
+
+- Bun workspaces - partial support; known issues
+- Nx - You can use Nx's [supported dependency strategies](https://nx.dev/concepts/decisions/dependency-management) but you need to have `package.json` files inside your workspace packages
+
+## Example monorepo
+
+In this example, the Mastra application is located at `apps/api`.
+
+```
+apps/
+├── api/
+│   ├── src/
+│   │   └── mastra/
+│   │       ├── agents/
+│   │       ├── tools/
+│   │       ├── workflows/
+│   │       └── index.ts
+│   ├── package.json
+│   └── tsconfig.json
+└── web/
+packages/
+├── ui/
+└── utils/
+package.json
+```
+
+## Environment variables
+
+Environment variables like `OPENAI_API_KEY` should be stored in an `.env` file at the root of the Mastra application `(apps/api)`, for example:
+
+```
+api/
+├── src/
+│   └── mastra/
+├── .env
+├── package.json
+└── tsconfig.json
+```
+
+## Deployment configuration
+
+The image below shows how to select `apps/api` as the project root when deploying to [Mastra Cloud](https://mastra.ai/docs/v1/mastra-cloud/overview). While the interface may differ between providers, the configuration remains the same.
+
+![Deployment configuration](/img/monorepo/monorepo-mastra-cloud.jpg)
+
+> **Note:**
+Make sure the correct package (e.g. `apps/api`) is selected as the deploy target. Selecting the wrong project root is a common deployment issue in monorepos.
+
+## Dependency management
+
+In a monorepo, keep dependencies consistent to avoid version conflicts and build errors.
+
+- Use a **single lockfile** at the project root so all packages resolve the same versions.
+- Align versions of **shared libraries** (like Mastra or frameworks) to prevent duplicates.

package/dist/docs/deployment/04-cloud-providers.md

@@ -0,0 +1,17 @@
+> Deploy your Mastra applications to cloud providers
+
+# Deploy to Cloud Providers
+
+Mastra applications can be deployed to cloud providers and serverless platforms. Mastra includes optional built-in deployers for Vercel, Netlify, and Cloudflare to automate the deployment process.
+
+## Supported Cloud Providers
+
+The following guides show how to deploy Mastra to specific cloud providers:
+
+- [Amazon EC2](https://mastra.ai/guides/v1/deployment/amazon-ec2)
+- [AWS Lambda](https://mastra.ai/guides/v1/deployment/aws-lambda)
+- [Azure App Services](https://mastra.ai/guides/v1/deployment/azure-app-services)
+- [Cloudflare](https://mastra.ai/guides/v1/deployment/cloudflare-deployer)
+- [Digital Ocean](https://mastra.ai/guides/v1/deployment/digital-ocean)
+- [Netlify](https://mastra.ai/guides/v1/deployment/netlify-deployer)
+- [Vercel](https://mastra.ai/guides/v1/deployment/vercel-deployer)

package/dist/docs/deployment/05-web-framework.md

@@ -0,0 +1,55 @@
+> Learn how Mastra can be deployed when integrated with a Web Framework
+
+# Deploy with a Web Framework
+
+When Mastra is integrated with a web framework, it deploys alongside your application using the framework's standard deployment process. Follow the instructions below to ensure your Mastra integration deploys correctly.
+
+> **Note:**
+If you're deploying to a cloud provider, remove any usage of [LibSQLStore](https://mastra.ai/reference/v1/storage/libsql) from your Mastra configuration. LibSQLStore requires filesystem access and is not compatible with serverless platforms.
+
+Integration guides:
+
+- [With Next.js](https://mastra.ai/guides/v1/getting-started/next-js)
+- [With Astro](https://mastra.ai/guides/v1/getting-started/astro)
+
+## With Next.js on Vercel
+
+If you've integrated Mastra with Next.js [by following our guide](https://mastra.ai/guides/v1/getting-started/next-js) and plan to deploy to Vercel, add `serverExternalPackages: ["@mastra/*"]` to your `next.config.ts`:
+
+```typescript {4} title="next.config.ts"
+import type { NextConfig } from "next";
+
+const nextConfig: NextConfig = {
+  serverExternalPackages: ["@mastra/*"],
+};
+
+export default nextConfig;
+```
+
+## With Astro on Vercel
+
+If you've integrated Mastra with Astro [by following our guide](https://mastra.ai/guides/v1/getting-started/astro) and plan to deploy to Vercel, add the Vercel adapter and server output to your `astro.config.mjs`:
+
+```javascript {2,5-6} title="astro.config.mjs"
+import { defineConfig } from "astro/config";
+import vercel from "@astrojs/vercel";
+
+export default defineConfig({
+  adapter: vercel(),
+  output: "server",
+});
+```
+
+## With Astro on Netlify
+
+If you've integrated Mastra with Astro [by following our guide](https://mastra.ai/guides/v1/getting-started/astro) and plan to deploy to Netlify, add the Netlify adapter and server output to your `astro.config.mjs`:
+
+```javascript {2,5-6} title="astro.config.mjs"
+import { defineConfig } from "astro/config";
+import netlify from "@astrojs/netlify";
+
+export default defineConfig({
+  adapter: netlify(),
+  output: "server",
+});
+```

package/dist/docs/deployment/06-workflow-runners.md

@@ -0,0 +1,11 @@
+> Deploy Mastra workflows to specialized workflow execution platforms
+
+# Workflow Runners
+
+Mastra [workflows](../workflows/overview.mdx) can be executed using the built-in workflow runner or deployed to specialized workflow execution platforms that handle orchestration, monitoring, and reliability.
+
+## Inngest
+
+Inngest is a developer platform for running background workflows without managing infrastructure. Mastra workflows can be deployed to Inngest, which provides step memoization, automatic retries, real-time monitoring, and suspend/resume capabilities.
+
+Visit the [Inngest deployment guide](https://mastra.ai/guides/v1/deployment/inngest) for setup instructions and the [Inngest workflow example](https://github.com/mastra-ai/mastra/tree/main/examples/inngest) for a complete implementation.

package/dist/effect-QlVUlMFu-HN3LWZSQ.cjs

@@ -0,0 +1,17 @@
+'use strict';
+
+var chunkJRUJ546M_cjs = require('./chunk-JRUJ546M.cjs');
+
+// ../../node_modules/.pnpm/@standard-community+standard-json@0.3.5_@standard-schema+spec@1.1.0_@types+json-schema@_d6df1f0b22bbb764c4c0abc17f6c5d32/node_modules/@standard-community/standard-json/dist/effect-QlVUlMFu.js
+async function getToJsonSchemaFn() {
+  try {
+    const { JSONSchema } = await import('effect');
+    return (schema) => JSONSchema.make(schema);
+  } catch {
+    throw new chunkJRUJ546M_cjs.MissingDependencyError("effect");
+  }
+}
+
+module.exports = getToJsonSchemaFn;
+//# sourceMappingURL=effect-QlVUlMFu-HN3LWZSQ.cjs.map
+//# sourceMappingURL=effect-QlVUlMFu-HN3LWZSQ.cjs.map

package/dist/effect-QlVUlMFu-HN3LWZSQ.cjs.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../node_modules/.pnpm/@standard-community+standard-json@0.3.5_@standard-schema+spec@1.1.0_@types+json-schema@_d6df1f0b22bbb764c4c0abc17f6c5d32/node_modules/@standard-community/standard-json/dist/effect-QlVUlMFu.js"],"names":["MissingDependencyError"],"mappings":";;;;;AAGA,eAAe,iBAAA,GAAoB;AACjC,EAAA,IAAI;AACF,IAAA,MAAM,EAAE,UAAA,EAAW,GAAI,MAAM,OAAO,QAAQ,CAAA;AAC5C,IAAA,OAAO,CAAC,MAAA,KAAW,UAAA,CAAW,IAAA,CAAK,MAAM,CAAA;AAAA,EAC3C,CAAA,CAAA,MAAQ;AACN,IAAA,MAAM,IAAIA,yCAAuB,QAAQ,CAAA;AAAA,EAC3C;AACF","file":"effect-QlVUlMFu-HN3LWZSQ.cjs","sourcesContent":["import { M as MissingDependencyError } from './index-CLddUTqr.js';\nimport 'quansync';\n\nasync function getToJsonSchemaFn() {\n  try {\n    const { JSONSchema } = await import('effect');\n    return (schema) => JSONSchema.make(schema);\n  } catch {\n    throw new MissingDependencyError(\"effect\");\n  }\n}\n\nexport { getToJsonSchemaFn as default };\n"]}

package/dist/effect-QlVUlMFu-XOJ2F4UA.js

@@ -0,0 +1,15 @@
+import { MissingDependencyError } from './chunk-DBXWQ2CA.js';
+
+// ../../node_modules/.pnpm/@standard-community+standard-json@0.3.5_@standard-schema+spec@1.1.0_@types+json-schema@_d6df1f0b22bbb764c4c0abc17f6c5d32/node_modules/@standard-community/standard-json/dist/effect-QlVUlMFu.js
+async function getToJsonSchemaFn() {
+  try {
+    const { JSONSchema } = await import('effect');
+    return (schema) => JSONSchema.make(schema);
+  } catch {
+    throw new MissingDependencyError("effect");
+  }
+}
+
+export { getToJsonSchemaFn as default };
+//# sourceMappingURL=effect-QlVUlMFu-XOJ2F4UA.js.map
+//# sourceMappingURL=effect-QlVUlMFu-XOJ2F4UA.js.map

package/dist/effect-QlVUlMFu-XOJ2F4UA.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../node_modules/.pnpm/@standard-community+standard-json@0.3.5_@standard-schema+spec@1.1.0_@types+json-schema@_d6df1f0b22bbb764c4c0abc17f6c5d32/node_modules/@standard-community/standard-json/dist/effect-QlVUlMFu.js"],"names":[],"mappings":";;;AAGA,eAAe,iBAAA,GAAoB;AACjC,EAAA,IAAI;AACF,IAAA,MAAM,EAAE,UAAA,EAAW,GAAI,MAAM,OAAO,QAAQ,CAAA;AAC5C,IAAA,OAAO,CAAC,MAAA,KAAW,UAAA,CAAW,IAAA,CAAK,MAAM,CAAA;AAAA,EAC3C,CAAA,CAAA,MAAQ;AACN,IAAA,MAAM,IAAI,uBAAuB,QAAQ,CAAA;AAAA,EAC3C;AACF","file":"effect-QlVUlMFu-XOJ2F4UA.js","sourcesContent":["import { M as MissingDependencyError } from './index-CLddUTqr.js';\nimport 'quansync';\n\nasync function getToJsonSchemaFn() {\n  try {\n    const { JSONSchema } = await import('effect');\n    return (schema) => JSONSchema.make(schema);\n  } catch {\n    throw new MissingDependencyError(\"effect\");\n  }\n}\n\nexport { getToJsonSchemaFn as default };\n"]}