@lovable.dev/mcp-js 0.22.1 → 0.22.2-rc.1

package/dist/stacks/tanstack/vite.d.cts

@@ -1,84 +1,83 @@
-import { Plugin } from 'vite';
-export { M as McpPluginApi } from '../../io-D4srzRKc.js';
-
+import { t as McpPluginApi } from "../../io-DPYvBqET.cjs";
+import { Plugin } from "vite";
+//#region src/stacks/tanstack/vite.d.ts
 interface McpPluginOptions {
-    /**
-     * Path to the MCP entry file (default export = `defineMcp(...)` result),
-     * relative to the project root.
-     * @default "src/lib/mcp/index.ts"
-     */
-    mcpEntry?: string;
-    /**
-     * Where TanStack route files live, relative to the project root.
-     * The plugin emits `<routesDir>/<routeFileName>` plus the REST companion
-     * routes here.
-     * @default "src/routes"
-     */
-    routesDir?: string;
-    /**
-     * Public URL path for the MCP-protocol route.
-     *
-     * The REST companion routes co-locate with this path under a `.mcp`
-     * sub-segment of the same parent prefix: `/mcp` keeps them at
-     * `/.mcp/list-tools` and `/.mcp/invoke-tool/$tool`, while
-     * `/api/public/mcp` moves them to `/api/public/.mcp/*`. The `.mcp`
-     * namespace keeps them from colliding with user-defined URLs without
-     * anchoring them at the root. Set `restRoutes: false` to drop the
-     * companions entirely.
-     *
-     * Must start with `/` and use only `/mcp`-style segments; anything more
-     * exotic doesn't map cleanly to a TanStack file name.
-     * @default "/mcp"
-     */
-    path?: string;
-    /**
-     * Filename to emit for the main MCP route, relative to `routesDir`.
-     * Defaults to a name derived from `path` (e.g. `/mcp` → `mcp.ts`,
-     * `/api/mcp` → `api/mcp.ts`).
-     */
-    routeFileName?: string;
-    /**
-     * Set to `false` to skip emitting the REST companion routes at
-     * `<path-parent>/.mcp/list-tools` and `<path-parent>/.mcp/<tool>`. Set
-     * `protectedResourceMetadataRoute: false` as well if you want the MCP
-     * protocol route to be the only emitted surface.
-     * @default true
-     */
-    restRoutes?: boolean;
-    /**
-     * Set to `false` to skip emitting the OAuth protected-resource metadata
-     * route at `/.well-known/oauth-protected-resource`.
-     * @default true
-     */
-    protectedResourceMetadataRoute?: boolean;
-    /**
-     * Public URL path for the OAuth protected-resource metadata route (RFC 9728).
-     * Both the emitted route file and the runtime `WWW-Authenticate` challenge use
-     * this path, so they can't drift. Use it when a host gate exposes only a
-     * sub-prefix (e.g. workspace-private projects where only `/api/public/*` is
-     * anonymously reachable) and the default well-known path is blocked.
-     *
-     * Leading-dot segments are bracket-escaped for TanStack file routing
-     * (`.well-known` → `[.well-known]`); the final segment becomes the route file.
-     * Mutually exclusive with `auth.protectedResourceMetadataUrl` (that option
-     * advertises an externally hosted document instead of serving one), and
-     * cannot be combined with `protectedResourceMetadataRoute: false`.
-     * @default "/.well-known/oauth-protected-resource"
-     */
-    metadataPath?: string;
-    /**
-     * Derive the public origin of the advertised OAuth `resource`/metadata URLs
-     * from `X-Forwarded-Host` instead of the rewritten `Host`. Lovable's web-proxy
-     * serves a custom domain by rewriting `Host` to the internal backend and
-     * overwriting `X-Forwarded-Host` with the real public host, so the default is
-     * `true` to make custom domains work out of the box. Set `false` only when
-     * deploying behind a proxy that does not overwrite the header (a client could
-     * then spoof it to redirect the advertised resource).
-     * @default true
-     */
-    trustForwardedHost?: boolean;
+  /**
+   * Path to the MCP entry file (default export = `defineMcp(...)` result),
+   * relative to the project root.
+   * @default "src/lib/mcp/index.ts"
+   */
+  mcpEntry?: string;
+  /**
+   * Where TanStack route files live, relative to the project root.
+   * The plugin emits `<routesDir>/<routeFileName>` plus the REST companion
+   * routes here.
+   * @default "src/routes"
+   */
+  routesDir?: string;
+  /**
+   * Public URL path for the MCP-protocol route.
+   *
+   * The REST companion routes co-locate with this path under a `.mcp`
+   * sub-segment of the same parent prefix: `/mcp` keeps them at
+   * `/.mcp/list-tools` and `/.mcp/invoke-tool/$tool`, while
+   * `/api/public/mcp` moves them to `/api/public/.mcp/*`. The `.mcp`
+   * namespace keeps them from colliding with user-defined URLs without
+   * anchoring them at the root. Set `restRoutes: false` to drop the
+   * companions entirely.
+   *
+   * Must start with `/` and use only `/mcp`-style segments; anything more
+   * exotic doesn't map cleanly to a TanStack file name.
+   * @default "/mcp"
+   */
+  path?: string;
+  /**
+   * Filename to emit for the main MCP route, relative to `routesDir`.
+   * Defaults to a name derived from `path` (e.g. `/mcp` → `mcp.ts`,
+   * `/api/mcp` → `api/mcp.ts`).
+   */
+  routeFileName?: string;
+  /**
+   * Set to `false` to skip emitting the REST companion routes at
+   * `<path-parent>/.mcp/list-tools` and `<path-parent>/.mcp/<tool>`. Set
+   * `protectedResourceMetadataRoute: false` as well if you want the MCP
+   * protocol route to be the only emitted surface.
+   * @default true
+   */
+  restRoutes?: boolean;
+  /**
+   * Set to `false` to skip emitting the OAuth protected-resource metadata
+   * route at `/.well-known/oauth-protected-resource`.
+   * @default true
+   */
+  protectedResourceMetadataRoute?: boolean;
+  /**
+   * Public URL path for the OAuth protected-resource metadata route (RFC 9728).
+   * Both the emitted route file and the runtime `WWW-Authenticate` challenge use
+   * this path, so they can't drift. Use it when a host gate exposes only a
+   * sub-prefix (e.g. workspace-private projects where only `/api/public/*` is
+   * anonymously reachable) and the default well-known path is blocked.
+   *
+   * Leading-dot segments are bracket-escaped for TanStack file routing
+   * (`.well-known` → `[.well-known]`); the final segment becomes the route file.
+   * Mutually exclusive with `auth.protectedResourceMetadataUrl` (that option
+   * advertises an externally hosted document instead of serving one), and
+   * cannot be combined with `protectedResourceMetadataRoute: false`.
+   * @default "/.well-known/oauth-protected-resource"
+   */
+  metadataPath?: string;
+  /**
+   * Derive the public origin of the advertised OAuth `resource`/metadata URLs
+   * from `X-Forwarded-Host` instead of the rewritten `Host`. Lovable's web-proxy
+   * serves a custom domain by rewriting `Host` to the internal backend and
+   * overwriting `X-Forwarded-Host` with the real public host, so the default is
+   * `true` to make custom domains work out of the box. Set `false` only when
+   * deploying behind a proxy that does not overwrite the header (a client could
+   * then spoof it to redirect the advertised resource).
+   * @default true
+   */
+  trustForwardedHost?: boolean;
 }
-
 declare function assertUrlPathShape(urlPath: string): string;
 declare function deriveRouteFileName(urlPath: string): string;
 declare function assertMetadataPathShape(metadataPath: string): void;
@@ -95,5 +94,5 @@ declare function assertMetadataPathShape(metadataPath: string): void;
  * time) — not by this plugin.
  */
 declare function mcpPlugin(options?: McpPluginOptions): Plugin;
-
-export { type McpPluginOptions, assertMetadataPathShape, assertUrlPathShape, mcpPlugin as default, deriveRouteFileName, mcpPlugin };
+//#endregion
+export { type McpPluginApi, McpPluginOptions, assertMetadataPathShape, assertUrlPathShape, mcpPlugin as default, mcpPlugin, deriveRouteFileName };

package/dist/stacks/tanstack/vite.d.ts

@@ -1,84 +1,83 @@
-import { Plugin } from 'vite';
-export { M as McpPluginApi } from '../../io-D4srzRKc.js';
-
+import { t as McpPluginApi } from "../../io-CfSPxeBN.js";
+import { Plugin } from "vite";
+//#region src/stacks/tanstack/vite.d.ts
 interface McpPluginOptions {
-    /**
-     * Path to the MCP entry file (default export = `defineMcp(...)` result),
-     * relative to the project root.
-     * @default "src/lib/mcp/index.ts"
-     */
-    mcpEntry?: string;
-    /**
-     * Where TanStack route files live, relative to the project root.
-     * The plugin emits `<routesDir>/<routeFileName>` plus the REST companion
-     * routes here.
-     * @default "src/routes"
-     */
-    routesDir?: string;
-    /**
-     * Public URL path for the MCP-protocol route.
-     *
-     * The REST companion routes co-locate with this path under a `.mcp`
-     * sub-segment of the same parent prefix: `/mcp` keeps them at
-     * `/.mcp/list-tools` and `/.mcp/invoke-tool/$tool`, while
-     * `/api/public/mcp` moves them to `/api/public/.mcp/*`. The `.mcp`
-     * namespace keeps them from colliding with user-defined URLs without
-     * anchoring them at the root. Set `restRoutes: false` to drop the
-     * companions entirely.
-     *
-     * Must start with `/` and use only `/mcp`-style segments; anything more
-     * exotic doesn't map cleanly to a TanStack file name.
-     * @default "/mcp"
-     */
-    path?: string;
-    /**
-     * Filename to emit for the main MCP route, relative to `routesDir`.
-     * Defaults to a name derived from `path` (e.g. `/mcp` → `mcp.ts`,
-     * `/api/mcp` → `api/mcp.ts`).
-     */
-    routeFileName?: string;
-    /**
-     * Set to `false` to skip emitting the REST companion routes at
-     * `<path-parent>/.mcp/list-tools` and `<path-parent>/.mcp/<tool>`. Set
-     * `protectedResourceMetadataRoute: false` as well if you want the MCP
-     * protocol route to be the only emitted surface.
-     * @default true
-     */
-    restRoutes?: boolean;
-    /**
-     * Set to `false` to skip emitting the OAuth protected-resource metadata
-     * route at `/.well-known/oauth-protected-resource`.
-     * @default true
-     */
-    protectedResourceMetadataRoute?: boolean;
-    /**
-     * Public URL path for the OAuth protected-resource metadata route (RFC 9728).
-     * Both the emitted route file and the runtime `WWW-Authenticate` challenge use
-     * this path, so they can't drift. Use it when a host gate exposes only a
-     * sub-prefix (e.g. workspace-private projects where only `/api/public/*` is
-     * anonymously reachable) and the default well-known path is blocked.
-     *
-     * Leading-dot segments are bracket-escaped for TanStack file routing
-     * (`.well-known` → `[.well-known]`); the final segment becomes the route file.
-     * Mutually exclusive with `auth.protectedResourceMetadataUrl` (that option
-     * advertises an externally hosted document instead of serving one), and
-     * cannot be combined with `protectedResourceMetadataRoute: false`.
-     * @default "/.well-known/oauth-protected-resource"
-     */
-    metadataPath?: string;
-    /**
-     * Derive the public origin of the advertised OAuth `resource`/metadata URLs
-     * from `X-Forwarded-Host` instead of the rewritten `Host`. Lovable's web-proxy
-     * serves a custom domain by rewriting `Host` to the internal backend and
-     * overwriting `X-Forwarded-Host` with the real public host, so the default is
-     * `true` to make custom domains work out of the box. Set `false` only when
-     * deploying behind a proxy that does not overwrite the header (a client could
-     * then spoof it to redirect the advertised resource).
-     * @default true
-     */
-    trustForwardedHost?: boolean;
+  /**
+   * Path to the MCP entry file (default export = `defineMcp(...)` result),
+   * relative to the project root.
+   * @default "src/lib/mcp/index.ts"
+   */
+  mcpEntry?: string;
+  /**
+   * Where TanStack route files live, relative to the project root.
+   * The plugin emits `<routesDir>/<routeFileName>` plus the REST companion
+   * routes here.
+   * @default "src/routes"
+   */
+  routesDir?: string;
+  /**
+   * Public URL path for the MCP-protocol route.
+   *
+   * The REST companion routes co-locate with this path under a `.mcp`
+   * sub-segment of the same parent prefix: `/mcp` keeps them at
+   * `/.mcp/list-tools` and `/.mcp/invoke-tool/$tool`, while
+   * `/api/public/mcp` moves them to `/api/public/.mcp/*`. The `.mcp`
+   * namespace keeps them from colliding with user-defined URLs without
+   * anchoring them at the root. Set `restRoutes: false` to drop the
+   * companions entirely.
+   *
+   * Must start with `/` and use only `/mcp`-style segments; anything more
+   * exotic doesn't map cleanly to a TanStack file name.
+   * @default "/mcp"
+   */
+  path?: string;
+  /**
+   * Filename to emit for the main MCP route, relative to `routesDir`.
+   * Defaults to a name derived from `path` (e.g. `/mcp` → `mcp.ts`,
+   * `/api/mcp` → `api/mcp.ts`).
+   */
+  routeFileName?: string;
+  /**
+   * Set to `false` to skip emitting the REST companion routes at
+   * `<path-parent>/.mcp/list-tools` and `<path-parent>/.mcp/<tool>`. Set
+   * `protectedResourceMetadataRoute: false` as well if you want the MCP
+   * protocol route to be the only emitted surface.
+   * @default true
+   */
+  restRoutes?: boolean;
+  /**
+   * Set to `false` to skip emitting the OAuth protected-resource metadata
+   * route at `/.well-known/oauth-protected-resource`.
+   * @default true
+   */
+  protectedResourceMetadataRoute?: boolean;
+  /**
+   * Public URL path for the OAuth protected-resource metadata route (RFC 9728).
+   * Both the emitted route file and the runtime `WWW-Authenticate` challenge use
+   * this path, so they can't drift. Use it when a host gate exposes only a
+   * sub-prefix (e.g. workspace-private projects where only `/api/public/*` is
+   * anonymously reachable) and the default well-known path is blocked.
+   *
+   * Leading-dot segments are bracket-escaped for TanStack file routing
+   * (`.well-known` → `[.well-known]`); the final segment becomes the route file.
+   * Mutually exclusive with `auth.protectedResourceMetadataUrl` (that option
+   * advertises an externally hosted document instead of serving one), and
+   * cannot be combined with `protectedResourceMetadataRoute: false`.
+   * @default "/.well-known/oauth-protected-resource"
+   */
+  metadataPath?: string;
+  /**
+   * Derive the public origin of the advertised OAuth `resource`/metadata URLs
+   * from `X-Forwarded-Host` instead of the rewritten `Host`. Lovable's web-proxy
+   * serves a custom domain by rewriting `Host` to the internal backend and
+   * overwriting `X-Forwarded-Host` with the real public host, so the default is
+   * `true` to make custom domains work out of the box. Set `false` only when
+   * deploying behind a proxy that does not overwrite the header (a client could
+   * then spoof it to redirect the advertised resource).
+   * @default true
+   */
+  trustForwardedHost?: boolean;
 }
-
 declare function assertUrlPathShape(urlPath: string): string;
 declare function deriveRouteFileName(urlPath: string): string;
 declare function assertMetadataPathShape(metadataPath: string): void;
@@ -95,5 +94,5 @@ declare function assertMetadataPathShape(metadataPath: string): void;
  * time) — not by this plugin.
  */
 declare function mcpPlugin(options?: McpPluginOptions): Plugin;
-
-export { type McpPluginOptions, assertMetadataPathShape, assertUrlPathShape, mcpPlugin as default, deriveRouteFileName, mcpPlugin };
+//#endregion
+export { type McpPluginApi, McpPluginOptions, assertMetadataPathShape, assertUrlPathShape, mcpPlugin as default, mcpPlugin, deriveRouteFileName };