boltdocs 2.9.1 → 2.9.3

package/dist/node/index.d.cts

@@ -1,9 +1,7 @@
 
+import { i as handleVercelFeedback, n as handleWebFeedback, r as handleNetlifyFeedback, t as handleAwsFeedback } from "../index-aWC0KjDF.cjs";
 import { InlineConfig, Plugin } from "vite";
 import { EXIT, SKIP } from "unist-util-visit";
-import { VercelRequest, VercelResponse } from "@vercel/node";
-import { HandlerEvent, HandlerResponse } from "@netlify/functions";
-import { Writable } from "node:stream";
 //#region src/shared/types.d.ts
 /**
  * Represents a single social link in the configuration.
@@ -729,274 +727,6 @@ declare const MDX_NODES: {
 //#region src/node/plugins/index.d.ts
 declare function createPlugin(plugin: SecureBoltdocsPlugin): SecureBoltdocsPlugin;
 //#endregion
-//#region src/node/feedback/adapters/vercel.d.ts
-declare function handleVercelFeedback(req: VercelRequest, res: VercelResponse): Promise<VercelResponse | undefined>;
-//#endregion
-//#region src/node/feedback/adapters/netlify.d.ts
-declare function handleNetlifyFeedback(event: HandlerEvent, env?: Record<string, string | undefined>): Promise<HandlerResponse>;
-//#endregion
-//#region src/node/feedback/adapters/web.d.ts
-declare function handleWebFeedback(request: Request, env?: Record<string, string | undefined>): Promise<Response>;
-//#endregion
-//#region ../../node_modules/.pnpm/@types+aws-lambda@8.10.161/node_modules/@types/aws-lambda/common/api-gateway.d.ts
-// Default authorizer type, prefer using a specific type with the "...WithAuthorizer..." variant types.
-// Note that this doesn't have to be a context from a custom lambda outhorizer, AWS also has a cognito
-// authorizer type and could add more, so the property won't always be a string.
-type APIGatewayEventDefaultAuthorizerContext = undefined | null | {
-  [name: string]: any;
-};
-// The requestContext property of both request authorizer and proxy integration events.
-interface APIGatewayEventRequestContextWithAuthorizer<TAuthorizerContext> {
-  accountId: string;
-  apiId: string; // This one is a bit confusing: it is not actually present in authorizer calls
-  // and proxy calls without an authorizer. We model this by allowing undefined in the type,
-  // since it ends up the same and avoids breaking users that are testing the property.
-  // This lets us allow parameterizing the authorizer for proxy events that know what authorizer
-  // context values they have.
-  authorizer: TAuthorizerContext;
-  connectedAt?: number | undefined;
-  connectionId?: string | undefined;
-  domainName?: string | undefined;
-  domainPrefix?: string | undefined;
-  eventType?: string | undefined;
-  extendedRequestId?: string | undefined;
-  protocol: string;
-  httpMethod: string;
-  identity: APIGatewayEventIdentity;
-  messageDirection?: string | undefined;
-  messageId?: string | null | undefined;
-  path: string;
-  stage: string;
-  requestId: string;
-  requestTime?: string | undefined;
-  requestTimeEpoch: number;
-  resourceId: string;
-  resourcePath: string;
-  routeKey?: string | undefined;
-}
-interface APIGatewayEventClientCertificate {
-  clientCertPem: string;
-  serialNumber: string;
-  subjectDN: string;
-  issuerDN: string;
-  validity: {
-    notAfter: string;
-    notBefore: string;
-  };
-}
-interface APIGatewayEventIdentity {
-  accessKey: string | null;
-  accountId: string | null;
-  apiKey: string | null;
-  apiKeyId: string | null;
-  caller: string | null;
-  clientCert: APIGatewayEventClientCertificate | null;
-  cognitoAuthenticationProvider: string | null;
-  cognitoAuthenticationType: string | null;
-  cognitoIdentityId: string | null;
-  cognitoIdentityPoolId: string | null;
-  principalOrgId: string | null;
-  sourceIp: string;
-  user: string | null;
-  userAgent: string | null;
-  userArn: string | null;
-  vpcId?: string | undefined;
-  vpceId?: string | undefined;
-}
-//#endregion
-//#region ../../node_modules/.pnpm/@types+aws-lambda@8.10.161/node_modules/@types/aws-lambda/handler.d.ts
-/**
- * {@link Handler} context parameter.
- * See {@link https://docs.aws.amazon.com/lambda/latest/dg/nodejs-prog-model-context.html AWS documentation}.
- */
-interface Context {
-  callbackWaitsForEmptyEventLoop: boolean;
-  functionName: string;
-  functionVersion: string;
-  invokedFunctionArn: string;
-  memoryLimitInMB: string;
-  awsRequestId: string;
-  logGroupName: string;
-  logStreamName: string;
-  identity?: CognitoIdentity | undefined;
-  clientContext?: ClientContext | undefined;
-  tenantId?: string | undefined;
-  getRemainingTimeInMillis(): number; // Functions for compatibility with earlier Node.js Runtime v0.10.42
-  // No longer documented, so they are deprecated, but they still work
-  // as of the 12.x runtime, so they are not removed from the types.
-  /** @deprecated Use handler callback or promise result */
-  done(error?: Error, result?: any): void;
-  /** @deprecated Use handler callback with first argument or reject a promise result */
-  fail(error: Error | string): void;
-  /** @deprecated Use handler callback with second argument or resolve a promise result */
-  succeed(messageOrObject: any): void; // Unclear what behavior this is supposed to have, I couldn't find any still extant reference,
-  // and it behaves like the above, ignoring the object parameter.
-  /** @deprecated Use handler callback or promise result */
-  succeed(message: string, object: any): void;
-}
-interface CognitoIdentity {
-  cognitoIdentityId: string;
-  cognitoIdentityPoolId: string;
-}
-interface ClientContext {
-  client: ClientContextClient;
-  custom?: any;
-  env: ClientContextEnv;
-}
-interface ClientContextClient {
-  installationId: string;
-  appTitle: string;
-  appVersionName: string;
-  appVersionCode: string;
-  appPackageName: string;
-}
-interface ClientContextEnv {
-  platformVersion: string;
-  platform: string;
-  make: string;
-  model: string;
-  locale: string;
-}
-/**
- * Interface for using response streaming from AWS Lambda.
- * To indicate to the runtime that Lambda should stream your function’s responses, you must wrap your function handler with the `awslambda.streamifyResponse()` decorator.
- *
- * The `streamifyResponse` decorator accepts the following additional parameter, `responseStream`, besides the default node handler parameters, `event`, and `context`.
- * The new `responseStream` object provides a stream object that your function can write data to. Data written to this stream is sent immediately to the client. You can optionally set the Content-Type header of the response to pass additional metadata to your client about the contents of the stream.
- *
- * {@link https://aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/ AWS blog post}
- * {@link https://docs.aws.amazon.com/lambda/latest/dg/config-rs-write-functions.html AWS documentation}
- *
- * @example <caption>Writing to the response stream</caption>
- * import 'aws-lambda';
- *
- * export const handler = awslambda.streamifyResponse(
- *   async (event, responseStream, context) => {
- *       responseStream.setContentType("text/plain");
- *       responseStream.write("Hello, world!");
- *       responseStream.end();
- *   }
- * );
- *
- * @example <caption>Using pipeline</caption>
- * import 'aws-lambda';
- * import { Readable } from 'stream';
- * import { pipeline } from 'stream/promises';
- * import zlib from 'zlib';
- *
- * export const handler = awslambda.streamifyResponse(
- *   async (event, responseStream, context) => {
- *     // As an example, convert event to a readable stream.
- *     const requestStream = Readable.from(Buffer.from(JSON.stringify(event)));
- *
- *     await pipeline(requestStream, zlib.createGzip(), responseStream);
- *   }
- * );
- */
-type StreamifyHandler<TEvent = any, TResult = any> = (event: TEvent, responseStream: awslambda.HttpResponseStream, context: Context) => TResult | Promise<TResult>;
-declare global {
-  namespace awslambda {
-    class HttpResponseStream extends Writable {
-      static from(writable: Writable, metadata: Record<string, unknown>): HttpResponseStream;
-      setContentType: (contentType: string) => void;
-    }
-    /**
-     * Decorator for using response streaming from AWS Lambda.
-     * To indicate to the runtime that Lambda should stream your function’s responses, you must wrap your function handler with the `awslambda.streamifyResponse()` decorator.
-     *
-     * The `streamifyResponse` decorator accepts the following additional parameter, `responseStream`, besides the default node handler parameters, `event`, and `context`.
-     * The new `responseStream` object provides a stream object that your function can write data to. Data written to this stream is sent immediately to the client. You can optionally set the Content-Type header of the response to pass additional metadata to your client about the contents of the stream.
-     *
-     * {@link https://aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/ AWS blog post}
-     * {@link https://docs.aws.amazon.com/lambda/latest/dg/config-rs-write-functions.html AWS documentation}
-     *
-     * @example <caption>Writing to the response stream</caption>
-     * import 'aws-lambda';
-     *
-     * export const handler = awslambda.streamifyResponse(
-     *   async (event, responseStream, context) => {
-     *       responseStream.setContentType("text/plain");
-     *       responseStream.write("Hello, world!");
-     *       responseStream.end();
-     *   }
-     * );
-     *
-     * @example <caption>Using pipeline</caption>
-     * import 'aws-lambda';
-     * import { Readable } from 'stream';
-     * import { pipeline } from 'stream/promises';
-     * import zlib from 'zlib';
-     *
-     * export const handler = awslambda.streamifyResponse(
-     *   async (event, responseStream, context) => {
-     *     // As an example, convert event to a readable stream.
-     *     const requestStream = Readable.from(Buffer.from(JSON.stringify(event)));
-     *
-     *     await pipeline(requestStream, zlib.createGzip(), responseStream);
-     *   }
-     * );
-     */
-    function streamifyResponse<TEvent = any, TResult = void>(handler: StreamifyHandler<TEvent, TResult>): StreamifyHandler<TEvent, TResult>;
-  }
-}
-//#endregion
-//#region ../../node_modules/.pnpm/@types+aws-lambda@8.10.161/node_modules/@types/aws-lambda/trigger/api-gateway-proxy.d.ts
-/**
- * Works with Lambda Proxy Integration for Rest API or HTTP API integration Payload Format version 1.0
- * @see - https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html
- */
-type APIGatewayProxyEvent = APIGatewayProxyEventBase<APIGatewayEventDefaultAuthorizerContext>;
-interface APIGatewayProxyEventHeaders {
-  [name: string]: string | undefined;
-}
-interface APIGatewayProxyEventMultiValueHeaders {
-  [name: string]: string[] | undefined;
-}
-interface APIGatewayProxyEventPathParameters {
-  [name: string]: string | undefined;
-}
-interface APIGatewayProxyEventQueryStringParameters {
-  [name: string]: string | undefined;
-}
-interface APIGatewayProxyEventMultiValueQueryStringParameters {
-  [name: string]: string[] | undefined;
-}
-interface APIGatewayProxyEventStageVariables {
-  [name: string]: string | undefined;
-}
-interface APIGatewayProxyEventBase<TAuthorizerContext> {
-  body: string | null;
-  headers: APIGatewayProxyEventHeaders;
-  multiValueHeaders: APIGatewayProxyEventMultiValueHeaders;
-  httpMethod: string;
-  isBase64Encoded: boolean;
-  path: string;
-  pathParameters: APIGatewayProxyEventPathParameters | null;
-  queryStringParameters: APIGatewayProxyEventQueryStringParameters | null;
-  multiValueQueryStringParameters: APIGatewayProxyEventMultiValueQueryStringParameters | null;
-  stageVariables: APIGatewayProxyEventStageVariables | null;
-  requestContext: APIGatewayEventRequestContextWithAuthorizer<TAuthorizerContext>;
-  resource: string;
-}
-/**
- * Works with Lambda Proxy Integration for Rest API or HTTP API integration Payload Format version 1.0
- * @see - https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html
- */
-interface APIGatewayProxyResult {
-  statusCode: number;
-  headers?: {
-    [header: string]: boolean | number | string;
-  } | undefined;
-  multiValueHeaders?: {
-    [header: string]: Array<boolean | number | string>;
-  } | undefined;
-  body: string;
-  isBase64Encoded?: boolean | undefined;
-}
-//#endregion
-//#region src/node/feedback/adapters/aws.d.ts
-declare function handleAwsFeedback(event: APIGatewayProxyEvent, env?: Record<string, string | undefined>): Promise<APIGatewayProxyResult>;
-//#endregion
 //#region src/node/feedback/handler.d.ts
 interface FeedbackHandlerOptions {
   owner?: string;

package/dist/node/index.d.mts

@@ -1,11 +1,8 @@
 
+import { i as handleVercelFeedback, n as handleWebFeedback, r as handleNetlifyFeedback, t as handleAwsFeedback } from "../index-ZqgZUvwp.mjs";
 import { z } from "zod";
-import { InlineConfig, Plugin } from "vite";
 import { EXIT, SKIP } from "unist-util-visit";
-import { VercelRequest, VercelResponse } from "@vercel/node";
-import { HandlerEvent, HandlerResponse } from "@netlify/functions";
-import { Writable } from "node:stream";
-
+import { InlineConfig, Plugin } from "vite";
 //#region src/shared/types.d.ts
 /**
  * Represents a single social link in the configuration.
@@ -731,274 +728,6 @@ declare const MDX_NODES: {
 //#region src/node/plugins/index.d.ts
 declare function createPlugin(plugin: SecureBoltdocsPlugin): SecureBoltdocsPlugin;
 //#endregion
-//#region src/node/feedback/adapters/vercel.d.ts
-declare function handleVercelFeedback(req: VercelRequest, res: VercelResponse): Promise<VercelResponse | undefined>;
-//#endregion
-//#region src/node/feedback/adapters/netlify.d.ts
-declare function handleNetlifyFeedback(event: HandlerEvent, env?: Record<string, string | undefined>): Promise<HandlerResponse>;
-//#endregion
-//#region src/node/feedback/adapters/web.d.ts
-declare function handleWebFeedback(request: Request, env?: Record<string, string | undefined>): Promise<Response>;
-//#endregion
-//#region ../../node_modules/.pnpm/@types+aws-lambda@8.10.161/node_modules/@types/aws-lambda/common/api-gateway.d.ts
-// Default authorizer type, prefer using a specific type with the "...WithAuthorizer..." variant types.
-// Note that this doesn't have to be a context from a custom lambda outhorizer, AWS also has a cognito
-// authorizer type and could add more, so the property won't always be a string.
-type APIGatewayEventDefaultAuthorizerContext = undefined | null | {
-  [name: string]: any;
-};
-// The requestContext property of both request authorizer and proxy integration events.
-interface APIGatewayEventRequestContextWithAuthorizer<TAuthorizerContext> {
-  accountId: string;
-  apiId: string; // This one is a bit confusing: it is not actually present in authorizer calls
-  // and proxy calls without an authorizer. We model this by allowing undefined in the type,
-  // since it ends up the same and avoids breaking users that are testing the property.
-  // This lets us allow parameterizing the authorizer for proxy events that know what authorizer
-  // context values they have.
-  authorizer: TAuthorizerContext;
-  connectedAt?: number | undefined;
-  connectionId?: string | undefined;
-  domainName?: string | undefined;
-  domainPrefix?: string | undefined;
-  eventType?: string | undefined;
-  extendedRequestId?: string | undefined;
-  protocol: string;
-  httpMethod: string;
-  identity: APIGatewayEventIdentity;
-  messageDirection?: string | undefined;
-  messageId?: string | null | undefined;
-  path: string;
-  stage: string;
-  requestId: string;
-  requestTime?: string | undefined;
-  requestTimeEpoch: number;
-  resourceId: string;
-  resourcePath: string;
-  routeKey?: string | undefined;
-}
-interface APIGatewayEventClientCertificate {
-  clientCertPem: string;
-  serialNumber: string;
-  subjectDN: string;
-  issuerDN: string;
-  validity: {
-    notAfter: string;
-    notBefore: string;
-  };
-}
-interface APIGatewayEventIdentity {
-  accessKey: string | null;
-  accountId: string | null;
-  apiKey: string | null;
-  apiKeyId: string | null;
-  caller: string | null;
-  clientCert: APIGatewayEventClientCertificate | null;
-  cognitoAuthenticationProvider: string | null;
-  cognitoAuthenticationType: string | null;
-  cognitoIdentityId: string | null;
-  cognitoIdentityPoolId: string | null;
-  principalOrgId: string | null;
-  sourceIp: string;
-  user: string | null;
-  userAgent: string | null;
-  userArn: string | null;
-  vpcId?: string | undefined;
-  vpceId?: string | undefined;
-}
-//#endregion
-//#region ../../node_modules/.pnpm/@types+aws-lambda@8.10.161/node_modules/@types/aws-lambda/handler.d.ts
-/**
- * {@link Handler} context parameter.
- * See {@link https://docs.aws.amazon.com/lambda/latest/dg/nodejs-prog-model-context.html AWS documentation}.
- */
-interface Context {
-  callbackWaitsForEmptyEventLoop: boolean;
-  functionName: string;
-  functionVersion: string;
-  invokedFunctionArn: string;
-  memoryLimitInMB: string;
-  awsRequestId: string;
-  logGroupName: string;
-  logStreamName: string;
-  identity?: CognitoIdentity | undefined;
-  clientContext?: ClientContext | undefined;
-  tenantId?: string | undefined;
-  getRemainingTimeInMillis(): number; // Functions for compatibility with earlier Node.js Runtime v0.10.42
-  // No longer documented, so they are deprecated, but they still work
-  // as of the 12.x runtime, so they are not removed from the types.
-  /** @deprecated Use handler callback or promise result */
-  done(error?: Error, result?: any): void;
-  /** @deprecated Use handler callback with first argument or reject a promise result */
-  fail(error: Error | string): void;
-  /** @deprecated Use handler callback with second argument or resolve a promise result */
-  succeed(messageOrObject: any): void; // Unclear what behavior this is supposed to have, I couldn't find any still extant reference,
-  // and it behaves like the above, ignoring the object parameter.
-  /** @deprecated Use handler callback or promise result */
-  succeed(message: string, object: any): void;
-}
-interface CognitoIdentity {
-  cognitoIdentityId: string;
-  cognitoIdentityPoolId: string;
-}
-interface ClientContext {
-  client: ClientContextClient;
-  custom?: any;
-  env: ClientContextEnv;
-}
-interface ClientContextClient {
-  installationId: string;
-  appTitle: string;
-  appVersionName: string;
-  appVersionCode: string;
-  appPackageName: string;
-}
-interface ClientContextEnv {
-  platformVersion: string;
-  platform: string;
-  make: string;
-  model: string;
-  locale: string;
-}
-/**
- * Interface for using response streaming from AWS Lambda.
- * To indicate to the runtime that Lambda should stream your function’s responses, you must wrap your function handler with the `awslambda.streamifyResponse()` decorator.
- *
- * The `streamifyResponse` decorator accepts the following additional parameter, `responseStream`, besides the default node handler parameters, `event`, and `context`.
- * The new `responseStream` object provides a stream object that your function can write data to. Data written to this stream is sent immediately to the client. You can optionally set the Content-Type header of the response to pass additional metadata to your client about the contents of the stream.
- *
- * {@link https://aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/ AWS blog post}
- * {@link https://docs.aws.amazon.com/lambda/latest/dg/config-rs-write-functions.html AWS documentation}
- *
- * @example <caption>Writing to the response stream</caption>
- * import 'aws-lambda';
- *
- * export const handler = awslambda.streamifyResponse(
- *   async (event, responseStream, context) => {
- *       responseStream.setContentType("text/plain");
- *       responseStream.write("Hello, world!");
- *       responseStream.end();
- *   }
- * );
- *
- * @example <caption>Using pipeline</caption>
- * import 'aws-lambda';
- * import { Readable } from 'stream';
- * import { pipeline } from 'stream/promises';
- * import zlib from 'zlib';
- *
- * export const handler = awslambda.streamifyResponse(
- *   async (event, responseStream, context) => {
- *     // As an example, convert event to a readable stream.
- *     const requestStream = Readable.from(Buffer.from(JSON.stringify(event)));
- *
- *     await pipeline(requestStream, zlib.createGzip(), responseStream);
- *   }
- * );
- */
-type StreamifyHandler<TEvent = any, TResult = any> = (event: TEvent, responseStream: awslambda.HttpResponseStream, context: Context) => TResult | Promise<TResult>;
-declare global {
-  namespace awslambda {
-    class HttpResponseStream extends Writable {
-      static from(writable: Writable, metadata: Record<string, unknown>): HttpResponseStream;
-      setContentType: (contentType: string) => void;
-    }
-    /**
-     * Decorator for using response streaming from AWS Lambda.
-     * To indicate to the runtime that Lambda should stream your function’s responses, you must wrap your function handler with the `awslambda.streamifyResponse()` decorator.
-     *
-     * The `streamifyResponse` decorator accepts the following additional parameter, `responseStream`, besides the default node handler parameters, `event`, and `context`.
-     * The new `responseStream` object provides a stream object that your function can write data to. Data written to this stream is sent immediately to the client. You can optionally set the Content-Type header of the response to pass additional metadata to your client about the contents of the stream.
-     *
-     * {@link https://aws.amazon.com/blogs/compute/introducing-aws-lambda-response-streaming/ AWS blog post}
-     * {@link https://docs.aws.amazon.com/lambda/latest/dg/config-rs-write-functions.html AWS documentation}
-     *
-     * @example <caption>Writing to the response stream</caption>
-     * import 'aws-lambda';
-     *
-     * export const handler = awslambda.streamifyResponse(
-     *   async (event, responseStream, context) => {
-     *       responseStream.setContentType("text/plain");
-     *       responseStream.write("Hello, world!");
-     *       responseStream.end();
-     *   }
-     * );
-     *
-     * @example <caption>Using pipeline</caption>
-     * import 'aws-lambda';
-     * import { Readable } from 'stream';
-     * import { pipeline } from 'stream/promises';
-     * import zlib from 'zlib';
-     *
-     * export const handler = awslambda.streamifyResponse(
-     *   async (event, responseStream, context) => {
-     *     // As an example, convert event to a readable stream.
-     *     const requestStream = Readable.from(Buffer.from(JSON.stringify(event)));
-     *
-     *     await pipeline(requestStream, zlib.createGzip(), responseStream);
-     *   }
-     * );
-     */
-    function streamifyResponse<TEvent = any, TResult = void>(handler: StreamifyHandler<TEvent, TResult>): StreamifyHandler<TEvent, TResult>;
-  }
-}
-//#endregion
-//#region ../../node_modules/.pnpm/@types+aws-lambda@8.10.161/node_modules/@types/aws-lambda/trigger/api-gateway-proxy.d.ts
-/**
- * Works with Lambda Proxy Integration for Rest API or HTTP API integration Payload Format version 1.0
- * @see - https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html
- */
-type APIGatewayProxyEvent = APIGatewayProxyEventBase<APIGatewayEventDefaultAuthorizerContext>;
-interface APIGatewayProxyEventHeaders {
-  [name: string]: string | undefined;
-}
-interface APIGatewayProxyEventMultiValueHeaders {
-  [name: string]: string[] | undefined;
-}
-interface APIGatewayProxyEventPathParameters {
-  [name: string]: string | undefined;
-}
-interface APIGatewayProxyEventQueryStringParameters {
-  [name: string]: string | undefined;
-}
-interface APIGatewayProxyEventMultiValueQueryStringParameters {
-  [name: string]: string[] | undefined;
-}
-interface APIGatewayProxyEventStageVariables {
-  [name: string]: string | undefined;
-}
-interface APIGatewayProxyEventBase<TAuthorizerContext> {
-  body: string | null;
-  headers: APIGatewayProxyEventHeaders;
-  multiValueHeaders: APIGatewayProxyEventMultiValueHeaders;
-  httpMethod: string;
-  isBase64Encoded: boolean;
-  path: string;
-  pathParameters: APIGatewayProxyEventPathParameters | null;
-  queryStringParameters: APIGatewayProxyEventQueryStringParameters | null;
-  multiValueQueryStringParameters: APIGatewayProxyEventMultiValueQueryStringParameters | null;
-  stageVariables: APIGatewayProxyEventStageVariables | null;
-  requestContext: APIGatewayEventRequestContextWithAuthorizer<TAuthorizerContext>;
-  resource: string;
-}
-/**
- * Works with Lambda Proxy Integration for Rest API or HTTP API integration Payload Format version 1.0
- * @see - https://docs.aws.amazon.com/apigateway/latest/developerguide/http-api-develop-integrations-lambda.html
- */
-interface APIGatewayProxyResult {
-  statusCode: number;
-  headers?: {
-    [header: string]: boolean | number | string;
-  } | undefined;
-  multiValueHeaders?: {
-    [header: string]: Array<boolean | number | string>;
-  } | undefined;
-  body: string;
-  isBase64Encoded?: boolean | undefined;
-}
-//#endregion
-//#region src/node/feedback/adapters/aws.d.ts
-declare function handleAwsFeedback(event: APIGatewayProxyEvent, env?: Record<string, string | undefined>): Promise<APIGatewayProxyResult>;
-//#endregion
 //#region src/node/feedback/handler.d.ts
 interface FeedbackHandlerOptions {
   owner?: string;

package/dist/node/index.mjs

@@ -3,4 +3,4 @@
  * Copyright (c) 2026 Jesus Alcala
  * Licensed under the MIT License.
  */
-import{A as e,C as t,D as n,M as r,N as i,O as a,S as o,_ as s,a as c,b as l,c as u,d,f,g as p,h as m,i as h,j as g,k as _,l as v,m as y,n as b,o as x,p as S,r as C,s as w,t as T,u as E,v as D,x as O,y as k}from"../node-B7qbjtLl.mjs";import{f as A,u as j}from"../utils-DexBrwiP.mjs";import{a as M,n as N}from"../config-DBKBEj3j.mjs";import{a as P,n as F}from"../cache-CfhOTR3Q.mjs";import{o as I,r as L}from"../shiki-adapter-rQ087Lx3.mjs";import{t as R}from"../handler-CyIBbZdb.mjs";export{F as AssetCache,a as BoltdocsPluginStore,u as EXIT,I as MDX_NODES,_ as PluginCompatibilityError,e as PluginError,g as PluginHookError,t as PluginLifecycleManager,r as PluginValidationError,v as SKIP,E as addNodeClass,d as createMdxAttribute,f as createMdxElement,w as createPlugin,S as createRehypeElement,b as createViteConfig,T as default,M as defineConfig,P as flushCache,i as generateEntryCode,y as getNodeProperty,C as handleAwsFeedback,R as handleFeedback,c as handleNetlifyFeedback,x as handleVercelFeedback,h as handleWebFeedback,m as hasNodeClass,j as normalizePath,L as parseMetaString,p as removeNodeClass,N as resolveConfig,A as sanitizeFilename,s as setNodeProperty,n as validatePlugins,D as visitMdxElements,k as visitNodes,l as visitRehypeElements,O as visitRemarkHeadings,o as visitRemarkLinks};
+import{C as e,D as t,E as n,O as r,T as i,_ as a,a as o,c as s,d as c,f as l,g as u,h as d,i as f,k as p,l as m,m as h,n as g,o as _,p as v,r as y,s as b,t as x,u as S,v as C,w,y as T}from"../node-JQ6C-CBi.mjs";import{f as E,u as D}from"../utils-DexBrwiP.mjs";import{a as O,n as k}from"../config-BCqkPkjC.mjs";import{a as A,n as j}from"../cache-CfhOTR3Q.mjs";import{o as M,r as N}from"../shiki-adapter-rQ087Lx3.mjs";import{t as P}from"../handler-CyIBbZdb.mjs";import{i as F,n as I,r as L,t as R}from"../adapters-HVuXENAe.mjs";export{j as AssetCache,w as BoltdocsPluginStore,f as EXIT,M as MDX_NODES,i as PluginCompatibilityError,n as PluginError,t as PluginHookError,T as PluginLifecycleManager,r as PluginValidationError,o as SKIP,_ as addNodeClass,b as createMdxAttribute,s as createMdxElement,y as createPlugin,m as createRehypeElement,g as createViteConfig,x as default,O as defineConfig,A as flushCache,p as generateEntryCode,S as getNodeProperty,R as handleAwsFeedback,P as handleFeedback,L as handleNetlifyFeedback,F as handleVercelFeedback,I as handleWebFeedback,c as hasNodeClass,D as normalizePath,N as parseMetaString,l as removeNodeClass,k as resolveConfig,E as sanitizeFilename,v as setNodeProperty,e as validatePlugins,h as visitMdxElements,d as visitNodes,u as visitRehypeElements,a as visitRemarkHeadings,C as visitRemarkLinks};

package/dist/node/routes/worker.cjs

@@ -3,4 +3,4 @@
  * Copyright (c) 2026 Jesus Alcala
  * Licensed under the MIT License.
  */
-require(`../../chunk-Ds5LZdWN.cjs`);const e=require(`../../parser-D4oEyuP-.cjs`);let t=require(`node:worker_threads`);if(!t.parentPort)throw Error(`This file must be run as a worker thread.`);t.parentPort.on(`message`,async n=>{if(n.type===`PARSE_FILE`)try{let r=await e.t(n.file,n.docsDir,n.basePath,n.config);t.parentPort?.postMessage({type:`SUCCESS`,file:n.file,result:r})}catch(e){t.parentPort?.postMessage({type:`ERROR`,file:n.file,error:e.message||`Unknown parsing error`})}});
+require(`../../chunk-Ds5LZdWN.cjs`);const e=require(`../../parser-CLtGv_XH.cjs`);let t=require(`node:worker_threads`);if(!t.parentPort)throw Error(`This file must be run as a worker thread.`);t.parentPort.on(`message`,async n=>{if(n.type===`PARSE_FILE`)try{let r=await e.t(n.file,n.docsDir,n.basePath,n.config);t.parentPort?.postMessage({type:`SUCCESS`,file:n.file,result:r})}catch(e){t.parentPort?.postMessage({type:`ERROR`,file:n.file,error:e.message||`Unknown parsing error`})}});

package/dist/node/routes/worker.mjs

@@ -3,4 +3,4 @@
  * Copyright (c) 2026 Jesus Alcala
  * Licensed under the MIT License.
  */
-import{n as e}from"../../parser-IR9tfyGE.mjs";import{parentPort as t}from"node:worker_threads";if(!t)throw Error(`This file must be run as a worker thread.`);t.on(`message`,async n=>{if(n.type===`PARSE_FILE`)try{let r=await e(n.file,n.docsDir,n.basePath,n.config);t?.postMessage({type:`SUCCESS`,file:n.file,result:r})}catch(e){t?.postMessage({type:`ERROR`,file:n.file,error:e.message||`Unknown parsing error`})}});export{};
+import{n as e}from"../../parser-Ww0eOqs7.mjs";import{parentPort as t}from"node:worker_threads";if(!t)throw Error(`This file must be run as a worker thread.`);t.on(`message`,async n=>{if(n.type===`PARSE_FILE`)try{let r=await e(n.file,n.docsDir,n.basePath,n.config);t?.postMessage({type:`SUCCESS`,file:n.file,result:r})}catch(e){t?.postMessage({type:`ERROR`,file:n.file,error:e.message||`Unknown parsing error`})}});export{};