@elizaos/plugin-mcp 1.7.0 → 2.0.0-alpha.1

package/dist/index.d.ts

@@ -1,7 +1,2 @@
-import { type Plugin } from "@elizaos/core";
-export * from "./types";
-export { McpService } from "./service";
-export { createMcpToolCompatibilitySync, createMcpToolCompatibility, detectModelProvider, McpToolCompatibility, type ModelInfo, type ModelProvider, type StringConstraints, type NumberConstraints, type ArrayConstraints, type ObjectConstraints, type SchemaConstraints, } from "./tool-compatibility";
-declare const mcpPlugin: Plugin;
-export default mcpPlugin;
-//# sourceMappingURL=index.d.ts.map
+export * from "./node/index";
+export { default } from "./node/index";

package/dist/node/actions/callToolAction.d.ts

@@ -0,0 +1,3 @@
+import type { Action } from "@elizaos/core";
+export declare const callToolAction: Action;
+//# sourceMappingURL=callToolAction.d.ts.map

package/dist/node/actions/callToolAction.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"callToolAction.d.ts","sourceRoot":"","sources":["../../../src/actions/callToolAction.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EACV,MAAM,EAMP,MAAM,eAAe,CAAC;AAQvB,eAAO,MAAM,cAAc,EAAE,MA2J5B,CAAC"}

package/dist/node/actions/readResourceAction.d.ts

@@ -0,0 +1,3 @@
+import { type Action } from "@elizaos/core";
+export declare const readResourceAction: Action;
+//# sourceMappingURL=readResourceAction.d.ts.map

package/dist/node/actions/readResourceAction.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"readResourceAction.d.ts","sourceRoot":"","sources":["../../../src/actions/readResourceAction.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,KAAK,MAAM,EAQZ,MAAM,eAAe,CAAC;AAqDvB,eAAO,MAAM,kBAAkB,EAAE,MA6KhC,CAAC"}

package/dist/node/generated/prompts/typescript/prompts.d.ts

@@ -0,0 +1,24 @@
+/**
+ * Auto-generated prompt templates
+ * DO NOT EDIT - Generated from ../../../../../prompts/*.txt
+ *
+ * These prompts use Handlebars-style template syntax:
+ * - {{variableName}} for simple substitution
+ * - {{#each items}}...{{/each}} for iteration
+ * - {{#if condition}}...{{/if}} for conditionals
+ */
+export declare const errorAnalysisTemplate = "{{{mcpProvider.text}}}\n\n{{{recentMessages}}}\n\n# Prompt\n\nYou're an assistant helping a user, but there was an error accessing the resource you tried to use.\n\nUser request: \"{{{userMessage}}}\"\nError message: {{{error}}}\n\nCreate a helpful response that:\n1. Acknowledges the issue in user-friendly terms\n2. Offers alternative approaches to help if possible\n3. Doesn't expose technical error details unless they're truly helpful\n4. Maintains a helpful, conversational tone\n\nYour response:";
+export declare const ERROR_ANALYSIS_TEMPLATE = "{{{mcpProvider.text}}}\n\n{{{recentMessages}}}\n\n# Prompt\n\nYou're an assistant helping a user, but there was an error accessing the resource you tried to use.\n\nUser request: \"{{{userMessage}}}\"\nError message: {{{error}}}\n\nCreate a helpful response that:\n1. Acknowledges the issue in user-friendly terms\n2. Offers alternative approaches to help if possible\n3. Doesn't expose technical error details unless they're truly helpful\n4. Maintains a helpful, conversational tone\n\nYour response:";
+export declare const feedbackTemplate = "{{{mcpProvider.text}}}\n\n{{{recentMessages}}}\n\n# Prompt\n\nYou previously attempted to parse a JSON selection but encountered an error. You need to fix the issues and provide a valid JSON response.\n\nPREVIOUS RESPONSE:\n{{{originalResponse}}\n\nERROR:\n{{{errorMessage}}\n\nAvailable {{{itemType}}}s:\n{{{itemsDescription}}\n\nUser request: \"{{{userMessage}}}\"\n\nCORRECTED INSTRUCTIONS:\n1. Create a valid JSON object that selects the most appropriate {{{itemType}}} for the task\n2. Make sure to use proper JSON syntax with double quotes for keys and string values\n3. Ensure all values exactly match the available {{{itemType}}}s (names are case-sensitive!)\n4. Do not include any markdown formatting, explanations, or non-JSON content\n5. Do not use placeholders - all values should be concrete and usable\n\nYOUR CORRECTED VALID JSON RESPONSE:";
+export declare const FEEDBACK_TEMPLATE = "{{{mcpProvider.text}}}\n\n{{{recentMessages}}}\n\n# Prompt\n\nYou previously attempted to parse a JSON selection but encountered an error. You need to fix the issues and provide a valid JSON response.\n\nPREVIOUS RESPONSE:\n{{{originalResponse}}\n\nERROR:\n{{{errorMessage}}\n\nAvailable {{{itemType}}}s:\n{{{itemsDescription}}\n\nUser request: \"{{{userMessage}}}\"\n\nCORRECTED INSTRUCTIONS:\n1. Create a valid JSON object that selects the most appropriate {{{itemType}}} for the task\n2. Make sure to use proper JSON syntax with double quotes for keys and string values\n3. Ensure all values exactly match the available {{{itemType}}}s (names are case-sensitive!)\n4. Do not include any markdown formatting, explanations, or non-JSON content\n5. Do not use placeholders - all values should be concrete and usable\n\nYOUR CORRECTED VALID JSON RESPONSE:";
+export declare const resourceAnalysisTemplate = "{{{mcpProvider.text}}}\n\n{{{recentMessages}}}\n\n# Prompt\n\nYou are a helpful assistant responding to a user's request. You've just accessed the resource \"{{{uri}}}\" to help answer this request.\n\nOriginal user request: \"{{{userMessage}}}\"\n\nResource metadata: \n{{{resourceMeta}}\n\nResource content: \n{{{resourceContent}}\n\nInstructions:\n1. Analyze how well the resource's content addresses the user's specific question or need\n2. Identify the most relevant information from the resource\n3. Create a natural, conversational response that incorporates this information\n4. If the resource content is insufficient, acknowledge its limitations and explain what you can determine\n5. Do not start with phrases like \"According to the resource\" or \"Here's what I found\" - instead, integrate the information naturally\n6. Maintain your helpful, intelligent assistant personality while presenting the information\n\nYour response (written as if directly to the user):";
+export declare const RESOURCE_ANALYSIS_TEMPLATE = "{{{mcpProvider.text}}}\n\n{{{recentMessages}}}\n\n# Prompt\n\nYou are a helpful assistant responding to a user's request. You've just accessed the resource \"{{{uri}}}\" to help answer this request.\n\nOriginal user request: \"{{{userMessage}}}\"\n\nResource metadata: \n{{{resourceMeta}}\n\nResource content: \n{{{resourceContent}}\n\nInstructions:\n1. Analyze how well the resource's content addresses the user's specific question or need\n2. Identify the most relevant information from the resource\n3. Create a natural, conversational response that incorporates this information\n4. If the resource content is insufficient, acknowledge its limitations and explain what you can determine\n5. Do not start with phrases like \"According to the resource\" or \"Here's what I found\" - instead, integrate the information naturally\n6. Maintain your helpful, intelligent assistant personality while presenting the information\n\nYour response (written as if directly to the user):";
+export declare const resourceSelectionTemplate = "{{{mcpProvider.text}}}\n\n{{{recentMessages}}}\n\n# Prompt\n\nYou are an intelligent assistant helping select the right resource to address a user's request.\n\nCRITICAL INSTRUCTIONS:\n1. You MUST specify both a valid serverName AND uri from the list above\n2. The serverName value should match EXACTLY the server name shown in parentheses (Server: X)\n   CORRECT: \"serverName\": \"github\"  (if the server is called \"github\") \n   WRONG: \"serverName\": \"GitHub\" or \"Github\" or any other variation\n3. The uri value should match EXACTLY the resource uri listed\n   CORRECT: \"uri\": \"weather://San Francisco/current\"  (if that's the exact uri)\n   WRONG: \"uri\": \"weather://sanfrancisco/current\" or any variation\n4. Identify the user's information need from the conversation context\n5. Select the most appropriate resource based on its description and the request\n6. If no resource seems appropriate, output {\"noResourceAvailable\": true}\n\n!!! YOUR RESPONSE MUST BE A VALID JSON OBJECT ONLY !!! \n\nSTRICT FORMAT REQUIREMENTS:\n- NO code block formatting (NO backticks or ```)\n- NO comments (NO // or /* */)\n- NO placeholders like \"replace with...\", \"example\", \"your...\", \"actual\", etc.\n- Every parameter value must be a concrete, usable value (not instructions to replace)\n- Use proper JSON syntax with double quotes for strings\n- NO explanatory text before or after the JSON object\n\nEXAMPLE RESPONSE:\n{\n  \"serverName\": \"weather-server\",\n  \"uri\": \"weather://San Francisco/current\",\n  \"reasoning\": \"Based on the conversation, the user is asking about current weather in San Francisco. This resource provides up-to-date weather information for that city.\"\n}\n\nREMEMBER: Your response will be parsed directly as JSON. If it fails to parse, the operation will fail completely!";
+export declare const RESOURCE_SELECTION_TEMPLATE = "{{{mcpProvider.text}}}\n\n{{{recentMessages}}}\n\n# Prompt\n\nYou are an intelligent assistant helping select the right resource to address a user's request.\n\nCRITICAL INSTRUCTIONS:\n1. You MUST specify both a valid serverName AND uri from the list above\n2. The serverName value should match EXACTLY the server name shown in parentheses (Server: X)\n   CORRECT: \"serverName\": \"github\"  (if the server is called \"github\") \n   WRONG: \"serverName\": \"GitHub\" or \"Github\" or any other variation\n3. The uri value should match EXACTLY the resource uri listed\n   CORRECT: \"uri\": \"weather://San Francisco/current\"  (if that's the exact uri)\n   WRONG: \"uri\": \"weather://sanfrancisco/current\" or any variation\n4. Identify the user's information need from the conversation context\n5. Select the most appropriate resource based on its description and the request\n6. If no resource seems appropriate, output {\"noResourceAvailable\": true}\n\n!!! YOUR RESPONSE MUST BE A VALID JSON OBJECT ONLY !!! \n\nSTRICT FORMAT REQUIREMENTS:\n- NO code block formatting (NO backticks or ```)\n- NO comments (NO // or /* */)\n- NO placeholders like \"replace with...\", \"example\", \"your...\", \"actual\", etc.\n- Every parameter value must be a concrete, usable value (not instructions to replace)\n- Use proper JSON syntax with double quotes for strings\n- NO explanatory text before or after the JSON object\n\nEXAMPLE RESPONSE:\n{\n  \"serverName\": \"weather-server\",\n  \"uri\": \"weather://San Francisco/current\",\n  \"reasoning\": \"Based on the conversation, the user is asking about current weather in San Francisco. This resource provides up-to-date weather information for that city.\"\n}\n\nREMEMBER: Your response will be parsed directly as JSON. If it fails to parse, the operation will fail completely!";
+export declare const toolReasoningTemplate = "{{{mcpProvider.text}}}\n\n{{{recentMessages}}}\n\n# Prompt\n\nYou are a helpful assistant responding to a user's request. You've just used the \"{{{toolName}}}\" tool from the \"{{{serverName}}}\" server to help answer this request.\n\nOriginal user request: \"{{{userMessage}}}\"\n\nTool response:\n{{{toolOutput}}}\n\n{{#if hasAttachments}}\nThe tool also returned images or other media that will be shared with the user.\n{{/if}}\n\nInstructions:\n1. Analyze how well the tool's response addresses the user's specific question or need\n2. Identify the most relevant information from the tool's output\n3. Create a natural, conversational response that incorporates this information\n4. If the tool's response is insufficient, acknowledge its limitations and explain what you can determine\n5. Do not start with phrases like \"I used the X tool\" or \"Here's what I found\" - instead, integrate the information naturally\n6. Maintain your helpful, intelligent assistant personality while presenting the information\n\nYour response (written as if directly to the user):";
+export declare const TOOL_REASONING_TEMPLATE = "{{{mcpProvider.text}}}\n\n{{{recentMessages}}}\n\n# Prompt\n\nYou are a helpful assistant responding to a user's request. You've just used the \"{{{toolName}}}\" tool from the \"{{{serverName}}}\" server to help answer this request.\n\nOriginal user request: \"{{{userMessage}}}\"\n\nTool response:\n{{{toolOutput}}}\n\n{{#if hasAttachments}}\nThe tool also returned images or other media that will be shared with the user.\n{{/if}}\n\nInstructions:\n1. Analyze how well the tool's response addresses the user's specific question or need\n2. Identify the most relevant information from the tool's output\n3. Create a natural, conversational response that incorporates this information\n4. If the tool's response is insufficient, acknowledge its limitations and explain what you can determine\n5. Do not start with phrases like \"I used the X tool\" or \"Here's what I found\" - instead, integrate the information naturally\n6. Maintain your helpful, intelligent assistant personality while presenting the information\n\nYour response (written as if directly to the user):";
+export declare const toolSelectionArgumentTemplate = "{{recentMessages}}\n\n# TASK: Generate a Strictly Valid JSON Object for Tool Execution\n\nYou have chosen the \"{{toolSelectionName.toolName}}\" tool from the \"{{toolSelectionName.serverName}}\" server to address the user's request.\nThe reasoning behind this selection is: \"{{toolSelectionName.reasoning}}\"\n\n## CRITICAL INSTRUCTIONS\n1. Ensure the \"toolArguments\" object strictly adheres to the structure and requirements defined in the schema.\n2. All parameter values must be extracted from the conversation context and must be concrete, usable values.\n3. Avoid placeholders or generic terms unless explicitly provided by the user.\n\n!!! YOUR RESPONSE MUST BE A VALID JSON OBJECT ONLY !!! \n\n## STRICT FORMAT REQUIREMENTS\n- The response MUST be a single valid JSON object.\n- DO NOT wrap the JSON in triple backticks (```), code blocks, or include any explanatory text.\n- DO NOT include comments (// or /* */) anywhere.\n- DO NOT use placeholders (e.g., \"replace with...\", \"example\", \"your...\", etc.)\n- ALL strings must use double quotes\n\n## CRITICAL NOTES\n- All values must be fully grounded in user input or inferred contextually.\n- No missing fields unless they are explicitly optional in the schema.\n- All types must match the schema (strings, numbers, booleans).\n\n## JSON OBJECT STRUCTURE\nYour response MUST contain ONLY these two top-level keys:\n1. \"toolArguments\" \u2014 An object matching the input schema: {{toolInputSchema}}\n2. \"reasoning\" \u2014 A string explaining how the values were inferred from the conversation.\n\n## EXAMPLE RESPONSE\n{\n  \"toolArguments\": {\n    \"owner\": \"facebook\",\n    \"repo\": \"react\",\n    \"path\": \"README.md\",\n    \"branch\": \"main\"\n  },\n  \"reasoning\": \"The user wants to see the README from the facebook/react repository based on our conversation.\"\n}\n\nREMEMBER: Your response will be parsed directly as JSON. If it fails to parse, the operation will fail completely.";
+export declare const TOOL_SELECTION_ARGUMENT_TEMPLATE = "{{recentMessages}}\n\n# TASK: Generate a Strictly Valid JSON Object for Tool Execution\n\nYou have chosen the \"{{toolSelectionName.toolName}}\" tool from the \"{{toolSelectionName.serverName}}\" server to address the user's request.\nThe reasoning behind this selection is: \"{{toolSelectionName.reasoning}}\"\n\n## CRITICAL INSTRUCTIONS\n1. Ensure the \"toolArguments\" object strictly adheres to the structure and requirements defined in the schema.\n2. All parameter values must be extracted from the conversation context and must be concrete, usable values.\n3. Avoid placeholders or generic terms unless explicitly provided by the user.\n\n!!! YOUR RESPONSE MUST BE A VALID JSON OBJECT ONLY !!! \n\n## STRICT FORMAT REQUIREMENTS\n- The response MUST be a single valid JSON object.\n- DO NOT wrap the JSON in triple backticks (```), code blocks, or include any explanatory text.\n- DO NOT include comments (// or /* */) anywhere.\n- DO NOT use placeholders (e.g., \"replace with...\", \"example\", \"your...\", etc.)\n- ALL strings must use double quotes\n\n## CRITICAL NOTES\n- All values must be fully grounded in user input or inferred contextually.\n- No missing fields unless they are explicitly optional in the schema.\n- All types must match the schema (strings, numbers, booleans).\n\n## JSON OBJECT STRUCTURE\nYour response MUST contain ONLY these two top-level keys:\n1. \"toolArguments\" \u2014 An object matching the input schema: {{toolInputSchema}}\n2. \"reasoning\" \u2014 A string explaining how the values were inferred from the conversation.\n\n## EXAMPLE RESPONSE\n{\n  \"toolArguments\": {\n    \"owner\": \"facebook\",\n    \"repo\": \"react\",\n    \"path\": \"README.md\",\n    \"branch\": \"main\"\n  },\n  \"reasoning\": \"The user wants to see the README from the facebook/react repository based on our conversation.\"\n}\n\nREMEMBER: Your response will be parsed directly as JSON. If it fails to parse, the operation will fail completely.";
+export declare const toolSelectionNameTemplate = "{{mcpProvider.text}}\n\n{{recentMessages}}\n\n# TASK: Select the Most Appropriate Tool and Server\n\nYou must select the most appropriate tool from the list above to fulfill the user's request. Your response must be a valid JSON object with the required properties.\n\n## CRITICAL INSTRUCTIONS\n1. Provide both \"serverName\" and \"toolName\" from the options listed above.\n2. Each name must match EXACTLY as shown in the list:\n   - Example (correct): \"serverName\": \"github\"\n   - Example (incorrect): \"serverName\": \"GitHub\", \"Github\", or variations\n3. Extract ACTUAL parameter values from the conversation context.\n   - Do not invent or use placeholders like \"octocat\" or \"Hello-World\" unless the user said so.\n4. Include a \"reasoning\" field explaining why the selected tool fits the request.\n5. If no tool is appropriate, respond with:\n   {\n     \"noToolAvailable\": true\n   }\n\n!!! YOUR RESPONSE MUST BE A VALID JSON OBJECT ONLY !!! \n\nCRITICAL: Your response must START with { and END with }. DO NOT include ANY text before or after the JSON.\n\n## STRICT FORMAT REQUIREMENTS\n- The response MUST be a single valid JSON object.\n- DO NOT wrap the JSON in triple backticks (```), code blocks, or include any explanatory text.\n- DO NOT include comments (// or /* */) anywhere.\n- DO NOT use placeholders (e.g., \"replace with...\", \"example\", \"your...\", etc.)\n- ALL strings must use double quotes.\n\n## CRITICAL NOTES\n- All values must be fully grounded in user input or inferred contextually.\n- No missing fields unless they are explicitly optional in the schema.\n- All types must match the schema (strings, numbers, booleans).\n\n## JSON OBJECT STRUCTURE\nYour response MUST contain ONLY these top-level keys:\n1. \"serverName\" \u2014 The name of the server (e.g., \"github\", \"notion\")\n2. \"toolName\" \u2014 The name of the tool (e.g., \"get_file_contents\", \"search\")\n3. \"reasoning\" \u2014 A string explaining how the values were inferred from the conversation.\n4. \"noToolAvailable\" \u2014 A boolean indicating if no tool is available (true/false)\n\n## EXAMPLE RESPONSE\n{\n  \"serverName\": \"github\",\n  \"toolName\": \"get_file_contents\",\n  \"reasoning\": \"The user wants to retrieve the README from the facebook/react repository.\",\n  \"noToolAvailable\": false\n}\n\n## REMINDERS\n- Use \"github\" as serverName for GitHub tools.\n- Use \"notion\" as serverName for Notion tools.\n- For search and knowledge-based tasks, MCP tools are often appropriate.\n\nREMEMBER: This output will be parsed directly as JSON. If the format is incorrect, the operation will fail.";
+export declare const TOOL_SELECTION_NAME_TEMPLATE = "{{mcpProvider.text}}\n\n{{recentMessages}}\n\n# TASK: Select the Most Appropriate Tool and Server\n\nYou must select the most appropriate tool from the list above to fulfill the user's request. Your response must be a valid JSON object with the required properties.\n\n## CRITICAL INSTRUCTIONS\n1. Provide both \"serverName\" and \"toolName\" from the options listed above.\n2. Each name must match EXACTLY as shown in the list:\n   - Example (correct): \"serverName\": \"github\"\n   - Example (incorrect): \"serverName\": \"GitHub\", \"Github\", or variations\n3. Extract ACTUAL parameter values from the conversation context.\n   - Do not invent or use placeholders like \"octocat\" or \"Hello-World\" unless the user said so.\n4. Include a \"reasoning\" field explaining why the selected tool fits the request.\n5. If no tool is appropriate, respond with:\n   {\n     \"noToolAvailable\": true\n   }\n\n!!! YOUR RESPONSE MUST BE A VALID JSON OBJECT ONLY !!! \n\nCRITICAL: Your response must START with { and END with }. DO NOT include ANY text before or after the JSON.\n\n## STRICT FORMAT REQUIREMENTS\n- The response MUST be a single valid JSON object.\n- DO NOT wrap the JSON in triple backticks (```), code blocks, or include any explanatory text.\n- DO NOT include comments (// or /* */) anywhere.\n- DO NOT use placeholders (e.g., \"replace with...\", \"example\", \"your...\", etc.)\n- ALL strings must use double quotes.\n\n## CRITICAL NOTES\n- All values must be fully grounded in user input or inferred contextually.\n- No missing fields unless they are explicitly optional in the schema.\n- All types must match the schema (strings, numbers, booleans).\n\n## JSON OBJECT STRUCTURE\nYour response MUST contain ONLY these top-level keys:\n1. \"serverName\" \u2014 The name of the server (e.g., \"github\", \"notion\")\n2. \"toolName\" \u2014 The name of the tool (e.g., \"get_file_contents\", \"search\")\n3. \"reasoning\" \u2014 A string explaining how the values were inferred from the conversation.\n4. \"noToolAvailable\" \u2014 A boolean indicating if no tool is available (true/false)\n\n## EXAMPLE RESPONSE\n{\n  \"serverName\": \"github\",\n  \"toolName\": \"get_file_contents\",\n  \"reasoning\": \"The user wants to retrieve the README from the facebook/react repository.\",\n  \"noToolAvailable\": false\n}\n\n## REMINDERS\n- Use \"github\" as serverName for GitHub tools.\n- Use \"notion\" as serverName for Notion tools.\n- For search and knowledge-based tasks, MCP tools are often appropriate.\n\nREMEMBER: This output will be parsed directly as JSON. If the format is incorrect, the operation will fail.";
+//# sourceMappingURL=prompts.d.ts.map

package/dist/node/generated/prompts/typescript/prompts.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../../../../../src/generated/prompts/typescript/prompts.ts"],"names":[],"mappings":"AAAA;;;;;;;;GAQG;AAEH,eAAO,MAAM,qBAAqB,2fAiBnB,CAAC;AAEhB,eAAO,MAAM,uBAAuB,2fAAwB,CAAC;AAE7D,eAAO,MAAM,gBAAgB,21BA0BO,CAAC;AAErC,eAAO,MAAM,iBAAiB,21BAAmB,CAAC;AAElD,eAAO,MAAM,wBAAwB,u9BAwBe,CAAC;AAErD,eAAO,MAAM,0BAA0B,u9BAA2B,CAAC;AAEnE,eAAO,MAAM,yBAAyB,syDAqC6E,CAAC;AAEpH,eAAO,MAAM,2BAA2B,syDAA4B,CAAC;AAErE,eAAO,MAAM,qBAAqB,ojCAyBkB,CAAC;AAErD,eAAO,MAAM,uBAAuB,ojCAAwB,CAAC;AAE7D,eAAO,MAAM,6BAA6B,u7DA0CyE,CAAC;AAEpH,eAAO,MAAM,gCAAgC,u7DAAgC,CAAC;AAE9E,eAAO,MAAM,yBAAyB,4kFAyDsE,CAAC;AAE7G,eAAO,MAAM,4BAA4B,4kFAA4B,CAAC"}

package/dist/node/index.d.ts

@@ -0,0 +1,4 @@
+import { type Plugin } from "@elizaos/core";
+declare const mcpPlugin: Plugin;
+export default mcpPlugin;
+//# sourceMappingURL=index.d.ts.map

package/dist/node/index.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/index.ts"],"names":[],"mappings":"AAAA,OAAO,EAA8B,KAAK,MAAM,EAAE,MAAM,eAAe,CAAC;AAMxE,QAAA,MAAM,SAAS,EAAE,MAWhB,CAAC;AAEF,eAAe,SAAS,CAAC"}