@analogjs/vite-plugin-nitro 3.0.0-alpha.7 → 3.0.0-alpha.70

package/src/lib/utils/server-fn-endpoints.d.ts

@@ -0,0 +1,41 @@
+import type { NitroEventHandler } from "nitropack";
+import type { ServerFnHandlerModule } from "./get-server-fn-handlers";
+/**
+* Nitro virtual-module id for the generated server-function dispatch handler.
+* Referenced from `nitroConfig.handlers` and provided via `nitroConfig.virtual`.
+*/
+export declare const SERVER_FN_DISPATCH_VIRTUAL = "#ANALOG_SERVER_FN_DISPATCH";
+/** The single transport route all server functions dispatch through. */
+export declare const SERVER_FN_DISPATCH_ROUTE = "/_analog/fn/:id";
+/** URL prefix of that route, for matching requests before the id is known. */
+export declare const SERVER_FN_DISPATCH_PREFIX = "/_analog/fn/";
+/**
+* The Nitro handler registration for the server-function dispatch route.
+* Unlike page endpoints (one handler per file), every server function shares
+* this one `/_analog/fn/:id` route; the id selects the function at runtime.
+*
+* The route is fixed and NOT `/api`-prefixed: client proxies always call the
+* absolute `/_analog/fn/:id` URL, so an `/api` prefix (as page endpoints use)
+* would leave the handler unreachable in apps that have an API directory.
+*/
+export declare function getServerFnDispatchHandler(): NitroEventHandler;
+export type BuildServerFnDispatchModuleArgs = {
+	/** Discovered `*.server.ts` modules, imported for registration side-effects. */
+	modules: ServerFnHandlerModule[];
+	/**
+	* Absolute path to the app's server config module (`app.config.server.ts`),
+	* which exports the `ApplicationConfig` (as `config`) that `main.server.ts`
+	* renders with. Handlers bootstrap against it, so they see the same DI the
+	* app configured. When absent, handlers run with only `providedIn: 'root'`.
+	*/
+	appConfigModule?: string;
+};
+/**
+* Generates the source of the Nitro dispatch handler.
+*
+* The handler imports every discovered `*.server.ts` module so each
+* `serverFn(...)` registers itself, imports the app's server config, then on
+* each request looks up the function by id and runs it via `dispatchServerFn` —
+* the same call path the validation harnesses exercise.
+*/
+export declare function buildServerFnDispatchModule({ modules, appConfigModule }: BuildServerFnDispatchModuleArgs): string;

package/src/lib/utils/server-fn-endpoints.js

@@ -0,0 +1,57 @@
+import { normalizePath } from "vite";
+//#region packages/vite-plugin-nitro/src/lib/utils/server-fn-endpoints.ts
+/**
+* Nitro virtual-module id for the generated server-function dispatch handler.
+* Referenced from `nitroConfig.handlers` and provided via `nitroConfig.virtual`.
+*/
+var SERVER_FN_DISPATCH_VIRTUAL = "#ANALOG_SERVER_FN_DISPATCH";
+/** The single transport route all server functions dispatch through. */
+var SERVER_FN_DISPATCH_ROUTE = "/_analog/fn/:id";
+/**
+* The Nitro handler registration for the server-function dispatch route.
+* Unlike page endpoints (one handler per file), every server function shares
+* this one `/_analog/fn/:id` route; the id selects the function at runtime.
+*
+* The route is fixed and NOT `/api`-prefixed: client proxies always call the
+* absolute `/_analog/fn/:id` URL, so an `/api` prefix (as page endpoints use)
+* would leave the handler unreachable in apps that have an API directory.
+*/
+function getServerFnDispatchHandler() {
+	return {
+		route: SERVER_FN_DISPATCH_ROUTE,
+		handler: SERVER_FN_DISPATCH_VIRTUAL,
+		lazy: true
+	};
+}
+/**
+* Generates the source of the Nitro dispatch handler.
+*
+* The handler imports every discovered `*.server.ts` module so each
+* `serverFn(...)` registers itself, imports the app's server config, then on
+* each request looks up the function by id and runs it via `dispatchServerFn` —
+* the same call path the validation harnesses exercise.
+*/
+function buildServerFnDispatchModule({ modules, appConfigModule }) {
+	return `import '@angular/compiler';
+import 'zone.js/node';
+import '@angular/platform-server/init';
+import { createServerFnAppInjector, createServerFnEventHandler } from '@analogjs/router/server';
+
+// Discovered server-function modules (registration side-effects).
+${modules.map((m) => `import ${JSON.stringify(normalizePath(m.file))};`).join("\n")}
+
+${appConfigModule ? `import { config as serverFnAppConfig } from ${JSON.stringify(normalizePath(appConfigModule))};` : `const serverFnAppConfig = { providers: [] };`}
+
+// Bootstrapped once from the app's own server config, so a handler resolves the
+// same DI as an SSR render (\`providedIn: 'root'\` and listed providers alike).
+// No component is bootstrapped, so nothing renders and the router never
+// navigates. Only REQUEST/RESPONSE are rebuilt per call.
+export default createServerFnEventHandler(
+  createServerFnAppInjector(serverFnAppConfig),
+);
+`;
+}
+//#endregion
+export { buildServerFnDispatchModule, getServerFnDispatchHandler };
+
+//# sourceMappingURL=server-fn-endpoints.js.map

package/src/lib/utils/server-fn-endpoints.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"server-fn-endpoints.js","names":[],"sources":["../../../../src/lib/utils/server-fn-endpoints.ts"],"sourcesContent":["import type { NitroEventHandler } from 'nitropack';\nimport { normalizePath } from 'vite';\n\nimport type { ServerFnHandlerModule } from './get-server-fn-handlers';\n\n/**\n * Nitro virtual-module id for the generated server-function dispatch handler.\n * Referenced from `nitroConfig.handlers` and provided via `nitroConfig.virtual`.\n */\nexport const SERVER_FN_DISPATCH_VIRTUAL = '#ANALOG_SERVER_FN_DISPATCH';\n\n/** The single transport route all server functions dispatch through. */\nexport const SERVER_FN_DISPATCH_ROUTE = '/_analog/fn/:id';\n\n/** URL prefix of that route, for matching requests before the id is known. */\nexport const SERVER_FN_DISPATCH_PREFIX = '/_analog/fn/';\n\n/**\n * The Nitro handler registration for the server-function dispatch route.\n * Unlike page endpoints (one handler per file), every server function shares\n * this one `/_analog/fn/:id` route; the id selects the function at runtime.\n *\n * The route is fixed and NOT `/api`-prefixed: client proxies always call the\n * absolute `/_analog/fn/:id` URL, so an `/api` prefix (as page endpoints use)\n * would leave the handler unreachable in apps that have an API directory.\n */\nexport function getServerFnDispatchHandler(): NitroEventHandler {\n  return {\n    route: SERVER_FN_DISPATCH_ROUTE,\n    handler: SERVER_FN_DISPATCH_VIRTUAL,\n    lazy: true,\n  };\n}\n\nexport type BuildServerFnDispatchModuleArgs = {\n  /** Discovered `*.server.ts` modules, imported for registration side-effects. */\n  modules: ServerFnHandlerModule[];\n  /**\n   * Absolute path to the app's server config module (`app.config.server.ts`),\n   * which exports the `ApplicationConfig` (as `config`) that `main.server.ts`\n   * renders with. Handlers bootstrap against it, so they see the same DI the\n   * app configured. When absent, handlers run with only `providedIn: 'root'`.\n   */\n  appConfigModule?: string;\n};\n\n/**\n * Generates the source of the Nitro dispatch handler.\n *\n * The handler imports every discovered `*.server.ts` module so each\n * `serverFn(...)` registers itself, imports the app's server config, then on\n * each request looks up the function by id and runs it via `dispatchServerFn` —\n * the same call path the validation harnesses exercise.\n */\nexport function buildServerFnDispatchModule({\n  modules,\n  appConfigModule,\n}: BuildServerFnDispatchModuleArgs): string {\n  const registrationImports = modules\n    .map((m) => `import ${JSON.stringify(normalizePath(m.file))};`)\n    .join('\\n');\n\n  // Bootstrap against the app's own server config so a handler resolves exactly\n  // the services, tokens, and interceptors the app configured — one config, no\n  // second provider list. Fall back to an empty config when the app has none.\n  const appConfig = appConfigModule\n    ? `import { config as serverFnAppConfig } from ${JSON.stringify(\n        normalizePath(appConfigModule),\n      )};`\n    : `const serverFnAppConfig = { providers: [] };`;\n\n  // `@analogjs/router/server` is a partially-compiled Angular library, and this\n  // module is bundled by Nitro rather than by the app's Angular pipeline, so the\n  // linker never runs over it. Loading the compiler gives it the JIT fallback.\n  // `zone.js` and the server platform init match the SSR entry, so bootstrapping\n  // the app injector below runs in the same environment a render would.\n  //\n  // The transport itself — id decoding, the malformed-body contract, dispatch,\n  // and response writing — lives in `createServerFnEventHandler`, so this module\n  // is only wiring: bootstrap the app injector from the app's server config, and\n  // hand it to that handler.\n  return `import '@angular/compiler';\nimport 'zone.js/node';\nimport '@angular/platform-server/init';\nimport { createServerFnAppInjector, createServerFnEventHandler } from '@analogjs/router/server';\n\n// Discovered server-function modules (registration side-effects).\n${registrationImports}\n\n${appConfig}\n\n// Bootstrapped once from the app's own server config, so a handler resolves the\n// same DI as an SSR render (\\`providedIn: 'root'\\` and listed providers alike).\n// No component is bootstrapped, so nothing renders and the router never\n// navigates. Only REQUEST/RESPONSE are rebuilt per call.\nexport default createServerFnEventHandler(\n  createServerFnAppInjector(serverFnAppConfig),\n);\n`;\n}\n"],"mappings":";;;;;;AASA,IAAa,6BAA6B;;AAG1C,IAAa,2BAA2B;;;;;;;;;;AAcxC,SAAgB,6BAAgD;AAC9D,QAAO;EACL,OAAO;EACP,SAAS;EACT,MAAM;EACP;;;;;;;;;;AAuBH,SAAgB,4BAA4B,EAC1C,SACA,mBAC0C;AAwB1C,QAAO;;;;;;EAvBqB,QACzB,KAAK,MAAM,UAAU,KAAK,UAAU,cAAc,EAAE,KAAK,CAAC,CAAC,GAAG,CAC9D,KAAK,KAAK,CA2BO;;EAtBF,kBACd,+CAA+C,KAAK,UAClD,cAAc,gBAAgB,CAC/B,CAAC,KACF,+CAoBM"}

package/src/lib/vite-plugin-nitro.d.ts

@@ -1,4 +1,4 @@
-import type { NitroConfig } from 'nitro/types';
-import type { Plugin } from 'vite';
-import { Options } from './options.js';
+import type { NitroConfig } from "nitro/types";
+import type { Plugin } from "vite";
+import { Options } from "./options.js";
 export declare function nitro(options?: Options, nitroOptions?: NitroConfig): Plugin[];