@mastra/deployer 0.0.0-error-handler-fix-20251020202607 → 0.0.0-esbuild-bundle-worker-20260807182016

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

@@ -0,0 +1,23 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# 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.
+
+## Mastra platform
+
+Mastra provides a platform to deploy your server to the cloud. Read the [Mastra platform deployment guide](https://mastra.ai/docs/mastra-platform/overview) to learn more.
+
+## Cloud providers
+
+The following guides show how to deploy Mastra to specific cloud providers:
+
+- [Amazon Bedrock AgentCore](https://mastra.ai/guides/deployment/aws-bedrock-agentcore)
+- [Amazon EC2](https://mastra.ai/guides/deployment/amazon-ec2)
+- [AWS Lambda](https://mastra.ai/guides/deployment/aws-lambda)
+- [Azure App Services](https://mastra.ai/guides/deployment/azure-app-services)
+- [Cloudflare](https://mastra.ai/guides/deployment/cloudflare)
+- [Digital Ocean](https://mastra.ai/guides/deployment/digital-ocean)
+- [Kubernetes](https://mastra.ai/guides/deployment/kubernetes)
+- [Netlify](https://mastra.ai/guides/deployment/netlify)
+- [Vercel](https://mastra.ai/guides/deployment/vercel)

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

@@ -0,0 +1,157 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# Deploy a Mastra server
+
+Mastra compiles your application into a standalone Node.js server that can run on any platform supporting Node.js, Bun, or Deno.
+
+> **Tip:** This guide covers deploying the standalone server generated by `mastra build`. If you need to integrate Mastra into an existing Express or Hono application, see [Server Adapters](https://mastra.ai/docs/server/server-adapters) instead.
+
+## Building your application
+
+Run the build command from your project root:
+
+```bash
+mastra build
+```
+
+This creates a `.mastra` directory containing your production-ready server. Read the [`mastra build`](https://mastra.ai/reference/cli/mastra) reference for all available flags.
+
+## Build output
+
+After building, Mastra creates the following structure:
+
+```text
+.mastra/
+├── .build/                # Intermediate build artifacts (module maps, analysis)
+└── output/
+    ├── index.mjs          # Server entry point
+    ├── mastra.mjs         # Your bundled Mastra configuration
+    ├── tools.mjs          # Aggregated tool exports
+    ├── tools/             # Individual tool bundles
+    ├── package.json       # Production dependencies
+    ├── node_modules/      # Installed dependencies
+    ├── .npmrc             # Copied from your project (if present)
+    ├── public/            # Static assets (if src/mastra/public exists)
+    └── playground/        # Studio UI (if --studio flag used)
+```
+
+The `output` directory is self-contained. You can copy it to any server and run it directly.
+
+## Running the server
+
+Start the server using the Mastra CLI:
+
+```bash
+mastra start
+```
+
+Or run directly with Node.js:
+
+```bash
+node .mastra/output/index.mjs
+```
+
+The `mastra start` command provides additional features:
+
+- Loads environment variables from `.env.production` and `.env`
+- Provides helpful error messages for missing modules
+- Handles process signals for graceful shutdown
+
+Read the [`mastra start`](https://mastra.ai/reference/cli/mastra) reference for all available flags.
+
+## Build configuration
+
+### Build-time configuration
+
+Mastra reads the `bundler`, `deployer`, and `server` options while it builds your application. Keep those options as direct properties of the object passed to `new Mastra()` so the build can extract them.
+
+The following entry-file shape works:
+
+```typescript
+import { Mastra } from '@mastra/core/mastra'
+
+export const mastra = new Mastra({
+  bundler: {
+    externals: ['sharp'],
+  },
+  server: {
+    port: 4111,
+  },
+})
+```
+
+The value of each option can come from a variable, import, or function call. The option itself must remain a direct property. Don't hide build-time options behind a factory call or an object spread:
+
+```typescript
+const options = {
+  bundler: {
+    externals: ['sharp'],
+  },
+}
+
+// These patterns prevent Mastra from extracting `bundler` during the build.
+export const mastra = new Mastra(createMastraOptions())
+export const otherMastra = new Mastra({ ...options })
+```
+
+When Mastra can't extract an option, it uses the default build behavior for that option. See the [configuration reference](https://mastra.ai/reference/configuration) for the available `bundler`, `deployer`, and `server` settings.
+
+### Public folder
+
+If a `public` folder exists in your Mastra directory (`src/mastra/public`), its contents are copied to the output directory during build. These files are served as static assets by the server.
+
+### Mastra configuration
+
+The build process respects configuration in your Mastra instance. For server behavior like CORS, timeouts, and middleware, see [server overview](https://mastra.ai/docs/server/mastra-server). For all available options, see the [configuration reference](https://mastra.ai/reference/configuration).
+
+## Build process
+
+The build follows these steps:
+
+1. **Locates entry file**: Finds `index.ts` or `index.js` in your Mastra directory.
+2. **Discovers tools**: Scans for tool files matching `{mastraDir}/tools/**/*.{js,ts}`, excluding test files.
+3. **Analyzes dependencies**: Determines which packages to bundle vs. install externally.
+4. **Bundles code**: Uses Rollup with tree-shaking and optional source maps.
+5. **Generates server**: Creates a Hono-based HTTP server as `index.mjs`.
+6. **Installs dependencies**: Runs `npm install` in the output directory.
+7. **Copies assets**: Copies `public` folder and `.npmrc` if present.
+
+## Environment variables
+
+| Variable             | Description                                                                 |
+| -------------------- | --------------------------------------------------------------------------- |
+| `PORT`               | Server port (default: `4111`)                                               |
+| `MASTRA_STUDIO_PATH` | Path to Studio build directory (default: `./playground`)                    |
+| `MASTRA_SKIP_DOTENV` | Skip loading `.env` files when set                                          |
+| `NODE_OPTIONS`       | Node.js options (e.g., `--max-old-space-size=4096` for build memory issues) |
+
+## Server endpoints
+
+The built server exposes endpoints for health checks, agents, workflows, and more:
+
+| Endpoint                | Description                                                            |
+| ----------------------- | ---------------------------------------------------------------------- |
+| `GET /health`           | Health check endpoint, returns `200 OK`                                |
+| `GET /api/openapi.json` | OpenAPI specification (if `server.build.openAPIDocs` is enabled).      |
+| `GET /swagger-ui`       | Interactive API documentation (if `server.build.swaggerUI` is enabled) |
+
+This list isn't exhaustive. To view all endpoints, run `mastra dev` and visit `http://localhost:4111/swagger-ui`.
+
+To add your own endpoints, see [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes).
+
+## Troubleshooting
+
+### Memory errors during build
+
+If you encounter `JavaScript heap out of memory` errors:
+
+```bash
+NODE_OPTIONS="--max-old-space-size=4096" mastra build
+```
+
+## Related
+
+- [Server Overview](https://mastra.ai/docs/server/mastra-server): Configure server behavior, middleware, and authentication
+- [Server Adapters](https://mastra.ai/docs/server/server-adapters): Use Express or Hono instead of `mastra build`
+- [Custom API Routes](https://mastra.ai/docs/server/custom-api-routes): Add custom HTTP endpoints
+- [Configuration Reference](https://mastra.ai/reference/configuration): Full configuration options

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

@@ -0,0 +1,140 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# Deploy in a monorepo
+
+Deploying Mastra in a monorepo follows the same process as a standalone application. This guide covers monorepo-specific considerations. For the core build and deployment steps, see [Deploy a Mastra Server](https://mastra.ai/docs/deployment/mastra-server).
+
+## 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 structure
+
+In this example, the Mastra application is located at `apps/api`:
+
+```text
+apps/
+├── api/
+│   ├── src/
+│   │   └── mastra/
+│   │       ├── agents/
+│   │       ├── tools/
+│   │       ├── workflows/
+│   │       └── index.ts
+│   ├── package.json
+│   └── tsconfig.json
+└── web/
+packages/
+├── ui/
+└── utils/
+package.json
+```
+
+## Building from a monorepo
+
+Use your monorepo tool to run the build command from the correct package. There's no need for special flags.
+
+Examples:
+
+**npm**:
+
+```bash
+npm run build --workspace=apps/api
+```
+
+**pnpm**:
+
+```bash
+pnpm --filter api run build
+```
+
+**yarn**:
+
+```bash
+yarn workspace api build
+```
+
+**Turborepo**:
+
+```bash
+turbo run build --filter=api
+```
+
+Your package's `build` script should run `mastra build`:
+
+```json
+{
+  "scripts": {
+    "build": "mastra build"
+  }
+}
+```
+
+## Workspace packages
+
+When your Mastra application imports from other workspace packages, Mastra handles this automatically:
+
+- If the package is pre-compiled (e.g., built with `tsc` or `tsdown`), Mastra imports the compiled JavaScript
+- If the package contains uncompiled TypeScript, Mastra transpiles it during the build
+
+For most setups, this works without configuration. If you encounter issues with workspace package imports, add the package to [`transpilePackages`](https://mastra.ai/reference/configuration):
+
+```typescript
+export const mastra = new Mastra({
+  bundler: {
+    transpilePackages: ['@my-org/utils'],
+  },
+})
+```
+
+Keep `bundler` as a direct property in the object passed to `new Mastra()`. See [build-time configuration](https://mastra.ai/docs/deployment/mastra-server) for the supported entry-file shape.
+
+## Environment variables
+
+Store `.env` files in the Mastra application directory (e.g., `apps/api/.env`), not the monorepo root.
+
+## Deployment configuration
+
+When deploying to cloud providers, ensure the correct package is selected as the deploy target. Selecting the monorepo root instead of the application directory (e.g., `apps/api`) is a common mistake.
+
+Most providers let you specify the root directory in their dashboard or configuration file.
+
+## Dependency management
+
+Keep dependencies consistent to avoid version conflicts and build errors:
+
+- Use a **single lockfile** at the monorepo root so all packages resolve the same versions
+- Align versions of **shared libraries** (like Mastra or frameworks) to prevent duplicates
+
+## Troubleshooting
+
+### Workspace package not found
+
+If Mastra can't resolve a workspace package, ensure:
+
+- The package is listed in your `package.json` dependencies
+- Your lockfile is up to date (`pnpm install`, `npm install`, etc.)
+- The package has a valid `main` or `exports` field in its `package.json`
+
+### TypeScript errors from workspace packages
+
+If you see type errors from uncompiled workspace packages, either:
+
+- Build the package first (recommended for faster Mastra builds)
+- Add the package to [`transpilePackages`](https://mastra.ai/reference/configuration) in your Mastra config
+
+## Related
+
+- [Deploy a Mastra Server](https://mastra.ai/docs/deployment/mastra-server): Core build and deployment guide
+- [Configuration Reference](https://mastra.ai/reference/configuration): `bundler.transpilePackages` and other options
+- [CLI Reference](https://mastra.ai/reference/cli/mastra): Build command flags

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

@@ -0,0 +1,79 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# 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 platform](https://mastra.ai/docs/mastra-platform/overview) for observability, Studio, and server deployment.
+
+## 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/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.
+
+Use this option when you need full control over your infrastructure, long-running processes, or WebSocket connections. The [Mastra server deployment guide](https://mastra.ai/docs/deployment/mastra-server) provides more details.
+
+### 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/deployment/monorepo).
+
+### Mastra platform
+
+The [Mastra platform](https://mastra.ai/docs/mastra-platform/overview) provides three products for deploying, monitoring, and managing AI applications built with the Mastra framework:
+
+- [**Observability**](https://mastra.ai/docs/mastra-platform/observability): A standalone hosted product for searchable traces, logs, and metrics across Mastra projects and deploys
+- [**Studio**](https://mastra.ai/docs/mastra-platform/studio): A hosted visual environment for testing agents and running workflows, plus inspecting traces
+- [**Server**](https://mastra.ai/docs/mastra-platform/server): A production deployment target that runs your Mastra application as an API server
+
+Learn more in the [Mastra platform overview](https://mastra.ai/docs/mastra-platform/overview).
+
+### 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.
+
+Use this option for auto-scaling, minimal infrastructure management, or when you're already using one of these platforms.
+
+- [Amazon EC2](https://mastra.ai/guides/deployment/amazon-ec2)
+- [AWS Lambda](https://mastra.ai/guides/deployment/aws-lambda)
+- [Azure App Services](https://mastra.ai/guides/deployment/azure-app-services)
+- [Cloudflare](https://mastra.ai/guides/deployment/cloudflare)
+- [Digital Ocean](https://mastra.ai/guides/deployment/digital-ocean)
+- [Kubernetes](https://mastra.ai/guides/deployment/kubernetes)
+- [Netlify](https://mastra.ai/guides/deployment/netlify)
+- [Vercel](https://mastra.ai/guides/deployment/vercel)
+
+### Sandbox
+
+Deploy a Mastra server into an ephemeral workspace sandbox (such as Vercel Sandbox or E2B) and get a live public URL in seconds.
+
+Use this option for instant previews, deploys from your CI pipeline, verifying agent-built apps, or running untrusted per-user instances. Read the [sandbox deployment guide](https://mastra.ai/docs/deployment/sandbox).
+
+### 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.
+
+Use these guides when adding Mastra to an existing Next.js or Astro application.
+
+- [With Next.js on Vercel](https://mastra.ai/docs/deployment/web-framework)
+- [With Astro on Vercel](https://mastra.ai/docs/deployment/web-framework)
+- [With Astro on Netlify](https://mastra.ai/docs/deployment/web-framework)
+
+## 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/deployment/workflow-runners) for execution options and the [Inngest deployment guide](https://mastra.ai/guides/deployment/inngest) for setup instructions.
+
+## Workers
+
+For production deployments, Mastra can run workflow orchestration, cron scheduling, and background tool execution in dedicated worker processes separate from the API server. This lets you scale each concern independently and isolate failures. See [Workers](https://mastra.ai/docs/deployment/workers) for details.

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

@@ -0,0 +1,54 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# 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.
+
+> **Warning:** If you're deploying to a cloud provider, remove any usage of [LibSQLStore](https://mastra.ai/reference/storage/libsql) from your Mastra configuration. LibSQLStore requires filesystem access and isn't compatible with serverless platforms.
+
+Integration guides:
+
+- [With Next.js](https://mastra.ai/guides/getting-started/next-js)
+- [With Astro](https://mastra.ai/guides/getting-started/astro)
+
+## With Next.js on Vercel
+
+If you've integrated Mastra with Next.js [by following our guide](https://mastra.ai/guides/getting-started/next-js) and plan to deploy to Vercel, add `serverExternalPackages: ["@mastra/*"]` to your `next.config.ts`:
+
+```typescript
+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/getting-started/astro) and plan to deploy to Vercel, add the Vercel adapter and server output to your `astro.config.mjs`:
+
+```javascript
+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/getting-started/astro) and plan to deploy to Netlify, add the Netlify adapter and server output to your `astro.config.mjs`:
+
+```javascript
+import { defineConfig } from 'astro/config'
+import netlify from '@astrojs/netlify'
+
+export default defineConfig({
+  adapter: netlify(),
+  output: 'server',
+})
+```

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

@@ -0,0 +1,17 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# Workflow runners
+
+Mastra [workflows](https://mastra.ai/docs/workflows/overview) 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/deployment/inngest) for setup instructions and the [Inngest workflow example](https://github.com/mastra-ai/mastra/tree/main/examples/inngest) for a complete implementation.
+
+## Temporal
+
+Temporal is a durable execution platform for orchestrating long-running workflows. Mastra workflows can run on Temporal workers, with each `createStep` mapped to a Temporal activity for automatic retries and durable state.
+
+The `@mastra/temporal` package is experimental and not ready for production use. Visit the [Temporal deployment guide](https://mastra.ai/guides/deployment/temporal) for setup instructions.

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

@@ -0,0 +1,102 @@
+> Discover all available pages from the documentation index: https://mastra.ai/llms.txt
+
+# Deployer
+
+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
+
+If you want to create a custom deployer, you can extend the abstract `Deployer` class and implement the `deploy` method with your specific deployment logic. Here's an example:
+
+```typescript
+import { Deployer } from '@mastra/deployer'
+
+class CustomDeployer extends Deployer {
+  constructor() {
+    super({ name: 'custom-deployer' })
+  }
+
+  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
+
+**args** (`object`): Configuration options for the Deployer.
+
+**args.name** (`string`): A unique name for the deployer instance.
+
+### deploy Parameters
+
+**outputDirectory** (`string`): The directory where the bundled and deployment-ready application will be output.
+
+## Methods
+
+**getEnvFiles** (`() => Promise<string[]>`): Returns a list of environment files to be used during deployment. By default, it looks for '.env.production' and '.env' files.
+
+**deploy** (`(outputDirectory: string) => Promise<void>`): Abstract method that must be implemented by subclasses. Handles the deployment process to the specified output directory.
+
+## Inherited methods from bundler
+
+The Deployer class inherits the following key methods from the Bundler class:
+
+**prepare** (`(outputDirectory: string) => Promise<void>`): Prepares the output directory by cleaning it and creating necessary subdirectories.
+
+**writePackageJson** (`(outputDirectory: string, dependencies: Map<string, string>) => Promise<void>`): Generates a package.json file in the output directory with the specified dependencies.
+
+**\_bundle** (`(serverFile: string, mastraEntryFile: string, outputDirectory: string, bundleLocation?: string) => Promise<void>`): Bundles the application using the specified server and Mastra entry files.
+
+## 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/effect-QlVUlMFu-CWx-dnsz.cjs

@@ -0,0 +1,14 @@
+const require_index_CLddUTqr = require("./index-CLddUTqr-C8lMvBz9.cjs");
+//#region ../../../../../setup-pnpm/node_modules/.bin/store/v11/links/@standard-community/standard-json/0.3.5/66cfaacd123cb91a4622503e450d47277c5e66dafdfc7e9d4c4d1c8f5b17d18e/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 require_index_CLddUTqr.MissingDependencyError("effect");
+	}
+}
+//#endregion
+exports.default = getToJsonSchemaFn;
+
+//# sourceMappingURL=effect-QlVUlMFu-CWx-dnsz.cjs.map

package/dist/effect-QlVUlMFu-CWx-dnsz.cjs.map

@@ -0,0 +1 @@
+{"version":3,"file":"effect-QlVUlMFu-CWx-dnsz.cjs","names":["MissingDependencyError"],"sources":["../../../../../../setup-pnpm/node_modules/.bin/store/v11/links/@standard-community/standard-json/0.3.5/66cfaacd123cb91a4622503e450d47277c5e66dafdfc7e9d4c4d1c8f5b17d18e/node_modules/@standard-community/standard-json/dist/effect-QlVUlMFu.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"],"x_google_ignoreList":[0],"mappings":";;AAGA,eAAe,oBAAoB;CACjC,IAAI;EACF,MAAM,EAAE,eAAe,MAAM,OAAO;EACpC,QAAQ,WAAW,WAAW,KAAK,MAAM;CAC3C,QAAQ;EACN,MAAM,IAAIA,uBAAAA,uBAAuB,QAAQ;CAC3C;AACF"}

package/dist/effect-QlVUlMFu-CovUzKO9.js

@@ -0,0 +1,14 @@
+import { t as MissingDependencyError } from "./index-CLddUTqr-Btqs8t-3.js";
+//#region ../../../../../setup-pnpm/node_modules/.bin/store/v11/links/@standard-community/standard-json/0.3.5/66cfaacd123cb91a4622503e450d47277c5e66dafdfc7e9d4c4d1c8f5b17d18e/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");
+	}
+}
+//#endregion
+export { getToJsonSchemaFn as default };
+
+//# sourceMappingURL=effect-QlVUlMFu-CovUzKO9.js.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"effect-QlVUlMFu-CovUzKO9.js","names":[],"sources":["../../../../../../setup-pnpm/node_modules/.bin/store/v11/links/@standard-community/standard-json/0.3.5/66cfaacd123cb91a4622503e450d47277c5e66dafdfc7e9d4c4d1c8f5b17d18e/node_modules/@standard-community/standard-json/dist/effect-QlVUlMFu.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"],"x_google_ignoreList":[0],"mappings":";;AAGA,eAAe,oBAAoB;CACjC,IAAI;EACF,MAAM,EAAE,eAAe,MAAM,OAAO;EACpC,QAAQ,WAAW,WAAW,KAAK,MAAM;CAC3C,QAAQ;EACN,MAAM,IAAI,uBAAuB,QAAQ;CAC3C;AACF"}