@pracht/vite-plugin 0.11.1 → 0.12.0

package/dist/pages-router.d.mts

@@ -1,6 +1,9 @@
+import { PAGES_APP_CONFIG_EXPORTS, findOwningPagesShell, pagesShellName } from "@pracht/capabilities/static";
+
 //#region src/pages-router.d.ts
 interface ScannedPage {
   absolutePath: string;
+  capabilities: string[];
   relativePath: string;
   routePath: string;
   isIndex: boolean;
@@ -8,6 +11,7 @@ interface ScannedPage {
   isDynamic: boolean;
   renderMode?: string;
   hydrationMode?: string;
+  streaming?: boolean;
   revalidateSeconds?: number;
   hasRevalidateExport?: boolean;
   hasLoader?: boolean;
@@ -18,14 +22,114 @@ interface PagesRouterOptions {
   pagesDir: string;
   pagesDefaultRender?: string;
   additionalExtensions?: readonly string[];
+  /**
+   * Absolute path of the capabilities directory. Every module in it is
+   * registered as a capability. Defaults to `<pagesDir>/../capabilities`, the
+   * `src/pages` + `src/capabilities` layout the plugin defaults to; pass `null`
+   * to register none.
+   */
+  capabilitiesDir?: string | null;
 }
+declare const GENERATED_PAGES_MANIFEST_MARKER = "Auto-generated from pages/ directory by @pracht/vite-plugin.";
+declare const GENERATED_PAGES_LAYOUT_EXPORT = "__PRACHT_EJECTED_PAGES_LAYOUT__";
+/**
+ * The root-level `_middleware.{ts,tsx,js,jsx}` file of a pages directory, or
+ * null when the app has none. Fails loudly on every shape that would
+ * otherwise fail open: a nested `_middleware` file, a `_middleware/`
+ * directory, any exact `_middleware` basename using an extension the runtime
+ * registry cannot load (all unsupported — they would be silently ignored while
+ * looking like an auth gate), and multiple root files competing for the same
+ * registration.
+ */
+declare function findPagesMiddlewareFile(pagesDir: string, _additionalExtensions?: readonly string[]): string | null;
+/** A discovered `_app` shell and the registration it owns. */
+interface PagesAppShell {
+  absolutePath: string;
+  /** Posix directory of the shell relative to the pages directory; `""` at the root. */
+  directory: string;
+  /** Registered shell name: `pages` at the root, `pages:blog` for `blog/_app.tsx`. */
+  name: string;
+}
+/** The registered shell name for an `_app` in `directory` (posix, `""` at the root). */
+/**
+ * Every `_app` shell in a pages directory, deepest first.
+ *
+ * An `_app` in a subdirectory owns the routes in that subtree: like a group's
+ * `shell` in an explicit manifest, the nearest one wins and REPLACES the
+ * parent rather than rendering inside it — `resolveApp()` gives every route
+ * exactly one shell, so file-system nesting cannot mean something the manifest
+ * router cannot express.
+ *
+ * Two `_app` files in the same directory are rejected: they compete for one
+ * registration, and picking either silently drops the other's `head()` and
+ * `headers()` from every route below.
+ */
+declare function findPagesAppShellFiles(pagesDir: string, shellExtensions: ReadonlySet<string>): PagesAppShell[];
+/**
+ * The app-level config file of a pages directory: `_app.config.ts` at the
+ * pages root.
+ *
+ * Named after the shell it configures, because that is what it is — the
+ * app-level knobs a manifest passes to `defineApp()` that no single route
+ * owns. It is root-only for the same reason `_middleware` is: `agents` and
+ * `constraints` are app-wide, so a per-directory copy would look scoped while
+ * being ignored.
+ */
+declare const PAGES_APP_CONFIG_BASENAME = "_app.config";
+/**
+ * The `defineApp` keys a pages app may set from `_app.config.ts`.
+ *
+ * Deliberately server-only keys. `notFound` is not one of them: the client
+ * router reads `app.notFound`, so accepting it here would pull this module —
+ * and its Web Bot Auth keys — into the browser bundle. `pages/404.tsx` is
+ * already the file convention for it.
+ */
+interface PagesAppConfig {
+  absolutePath: string;
+  /** The subset of PAGES_APP_CONFIG_EXPORTS the module actually exports. */
+  exports: string[];
+}
+/**
+ * The root-level `_app.config.{ts,tsx,js,jsx}` of a pages directory, or null
+ * when the app has none.
+ *
+ * Fails closed on every shape that would otherwise leave an app looking
+ * configured while nothing is registered: a nested file, an unsupported
+ * extension, duplicates, a module that exports none of the supported keys, and
+ * a value `export *` whose names cannot be known without loading the module.
+ */
+declare function findPagesAppConfigFile(pagesDir: string): PagesAppConfig | null;
+/** A capability module auto-discovered from the capabilities directory. */
+interface PagesCapability {
+  absolutePath: string;
+  name: string;
+}
+/**
+ * Every capability module in `capabilitiesDir`, keyed by the name it registers
+ * under.
+ *
+ * The pages router has no `capabilities` registry, so the directory *is* the
+ * registry: one module per capability, named by `defineCapability({ name })`
+ * or by its file stem. That keeps registration explicit — a file has to be in
+ * `src/capabilities/` to be reachable — without inventing a second place to
+ * repeat the name.
+ */
+declare function findPagesCapabilityFiles(capabilitiesDir: string): PagesCapability[];
 declare function scanPagesDirectory(pagesDir: string, additionalExtensions?: readonly string[]): ScannedPage[];
 declare function filePathToRoutePath(relativePath: string): string;
 declare function sortRoutes(pages: ScannedPage[]): ScannedPage[];
 declare function generatePagesManifestSource(pages: ScannedPage[], options: PagesRouterOptions & {
+  /** Project-root-relative capabilities prefix (e.g. `/src/capabilities`). */capabilitiesDirPrefix?: string;
   pagesDirPrefix?: string;
+  referenceBaseDir?: string;
+  /**
+   * `"client"` omits the keys only the server reads (`agents`,
+   * `constraints`) and the `_app.config.ts` import that supplies them, so
+   * that module and everything it imports stay out of browser bundles.
+   */
+  target?: "server" | "client";
   useImportSyntax?: boolean;
 }): string;
 declare function generateRoutesFile(pagesDir: string, outputPath: string, options: PagesRouterOptions): void;
 //#endregion
-export { PagesRouterOptions, ScannedPage, filePathToRoutePath, generatePagesManifestSource, generateRoutesFile, scanPagesDirectory, sortRoutes };
+export { GENERATED_PAGES_LAYOUT_EXPORT, GENERATED_PAGES_MANIFEST_MARKER, PAGES_APP_CONFIG_BASENAME, PAGES_APP_CONFIG_EXPORTS, PagesAppConfig, PagesAppShell, PagesCapability, PagesRouterOptions, ScannedPage, filePathToRoutePath, findOwningPagesShell, findPagesAppConfigFile, findPagesAppShellFiles, findPagesCapabilityFiles, findPagesMiddlewareFile, generatePagesManifestSource, generateRoutesFile, pagesShellName, scanPagesDirectory, sortRoutes };

package/dist/pages-router.mjs

@@ -1,2 +1,2 @@
-import { a as sortRoutes, i as scanPagesDirectory, n as generatePagesManifestSource, r as generateRoutesFile, t as filePathToRoutePath } from "./pages-router-MA9rOl88.mjs";
-export { filePathToRoutePath, generatePagesManifestSource, generateRoutesFile, scanPagesDirectory, sortRoutes };
+import { a as filePathToRoutePath, c as findPagesAppShellFiles, d as generatePagesManifestSource, f as generateRoutesFile, h as sortRoutes, i as PAGES_APP_CONFIG_EXPORTS, l as findPagesCapabilityFiles, m as scanPagesDirectory, n as GENERATED_PAGES_MANIFEST_MARKER, o as findOwningPagesShell, p as pagesShellName, r as PAGES_APP_CONFIG_BASENAME, s as findPagesAppConfigFile, t as GENERATED_PAGES_LAYOUT_EXPORT, u as findPagesMiddlewareFile } from "./pages-router-BI34Cani.mjs";
+export { GENERATED_PAGES_LAYOUT_EXPORT, GENERATED_PAGES_MANIFEST_MARKER, PAGES_APP_CONFIG_BASENAME, PAGES_APP_CONFIG_EXPORTS, filePathToRoutePath, findOwningPagesShell, findPagesAppConfigFile, findPagesAppShellFiles, findPagesCapabilityFiles, findPagesMiddlewareFile, generatePagesManifestSource, generateRoutesFile, pagesShellName, scanPagesDirectory, sortRoutes };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pracht/vite-plugin",
-  "version": "0.11.1",
+  "version": "0.12.0",
   "description": "Vite plugin for Pracht apps with virtual modules, dev SSR, prerendering, route inspection, and multi-adapter builds.",
   "keywords": [
     "pracht",
@@ -42,6 +42,9 @@
       "types": "./virtual.d.ts"
     }
   },
+  "engines": {
+    "node": ">=22.18"
+  },
   "publishConfig": {
     "provenance": true
   },
@@ -50,10 +53,10 @@
     "@preact/preset-vite": "^2.10.5",
     "@prefresh/vite": "^2.0.0",
     "es-module-lexer": "^1.7.0",
-    "@pracht/adapter-node": "0.4.2",
-    "@pracht/capabilities": "0.3.0",
-    "@pracht/core": "0.16.0",
-    "@pracht/preact-ssr-precompile": "0.1.3"
+    "@pracht/adapter-node": "0.4.3",
+    "@pracht/capabilities": "0.4.0",
+    "@pracht/preact-ssr-precompile": "0.1.4",
+    "@pracht/core": "0.17.0"
   },
   "peerDependencies": {
     "vite": "^8.0.0"

package/virtual.d.ts

@@ -243,8 +243,8 @@ declare module "virtual:pracht/capabilities" {
 }
 
 declare module "virtual:pracht/webmcp" {
-  /** Registers WebMCP page tools; returns false when the API is unavailable. */
-  export function registerPrachtWebmcpTools(): boolean;
+  /** Replaces the active route's WebMCP page tools; returns false when the API is unavailable. */
+  export function registerPrachtWebmcpTools(capabilities: readonly string[]): boolean;
 }
 
 // Preserve the ambient declaration shipped with Pracht's compatibility-level