@payloadcms/tanstack-start 4.0.0-internal.17c142b → 4.0.0-internal.1a2a79e

package/dist/utilities/initAdminContext.server.js

@@ -0,0 +1,13 @@
+import { getRequest } from '@tanstack/react-start/server';
+import { initAdminContext as initPayloadAdminContext } from 'payload/internal';
+// Registers the dev reload strategy before `initPayloadAdminContext` can build an instance.
+// Side-effect only, and a no-op outside of dev serve.
+import './devConfigReload.server.js';
+import { tanstackServerAdapter } from '../adapters/server.js';
+export const initAdminContext = ({ serverAdapter = tanstackServerAdapter, ...args })=>initPayloadAdminContext({
+        ...args,
+        requestURL: getRequest().url,
+        serverAdapter
+    });
+
+//# sourceMappingURL=initAdminContext.server.js.map

package/dist/utilities/initAdminContext.server.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/utilities/initAdminContext.server.ts"],"sourcesContent":["import type { ServerAdapter } from 'payload'\nimport type { InitAdminContextArgs } from 'payload/internal'\n\nimport { getRequest } from '@tanstack/react-start/server'\nimport { initAdminContext as initPayloadAdminContext } from 'payload/internal'\n\n// Registers the dev reload strategy before `initPayloadAdminContext` can build an instance.\n// Side-effect only, and a no-op outside of dev serve.\nimport './devConfigReload.server.js'\nimport { tanstackServerAdapter } from '../adapters/server.js'\n\ntype TanStackInitAdminContextArgs = {\n  serverAdapter?: ServerAdapter\n} & Omit<InitAdminContextArgs, 'cache' | 'requestURL' | 'serverAdapter'>\n\nexport const initAdminContext = ({\n  serverAdapter = tanstackServerAdapter,\n  ...args\n}: TanStackInitAdminContextArgs) =>\n  initPayloadAdminContext({\n    ...args,\n    requestURL: getRequest().url,\n    serverAdapter,\n  })\n"],"names":["getRequest","initAdminContext","initPayloadAdminContext","tanstackServerAdapter","serverAdapter","args","requestURL","url"],"mappings":"AAGA,SAASA,UAAU,QAAQ,+BAA8B;AACzD,SAASC,oBAAoBC,uBAAuB,QAAQ,mBAAkB;AAE9E,4FAA4F;AAC5F,sDAAsD;AACtD,OAAO,8BAA6B;AACpC,SAASC,qBAAqB,QAAQ,wBAAuB;AAM7D,OAAO,MAAMF,mBAAmB,CAAC,EAC/BG,gBAAgBD,qBAAqB,EACrC,GAAGE,MAC0B,GAC7BH,wBAAwB;QACtB,GAAGG,IAAI;QACPC,YAAYN,aAAaO,GAAG;QAC5BH;IACF,GAAE"}

package/dist/utilities/routerSearch.d.ts

@@ -0,0 +1,40 @@
+import * as qs from 'qs-esm';
+/**
+ * `parseSearch` for TanStack Router's `createRouter`, required for Payload's
+ * admin UI. Pair with {@link payloadStringifySearch}.
+ *
+ * Payload serializes query state (notably the list-view `where` filter) with
+ * `qs` bracket notation — e.g. `?where[or][0][and][0][x][equals]=y`. TanStack
+ * Router's default serializer treats each bracketed string as a flat key and
+ * JSON-encodes values, so it never round-trips Payload's nested query: every
+ * navigation re-encodes the already-encoded value, exponentially nesting it
+ * (`[true,"[true,\"[true…"]`) until the filter is unusable. Parsing and
+ * stringifying with `qs` (same options as `payload`/`@payloadcms/ui`) keeps
+ * the URL idempotent and the nested `where` intact across navigations.
+ *
+ * This is a router-global serializer: it applies to every route, not just
+ * `/admin`. On your own routes, search values arrive as strings (qs does no
+ * JSON type-coercion), so coerce in `validateSearch` (e.g. `Number(...)`) where
+ * you need numbers or booleans.
+ *
+ * @example
+ * ```ts
+ * import { createRouter } from '@tanstack/react-router'
+ * import { payloadParseSearch, payloadStringifySearch } from '@payloadcms/tanstack-start/shared'
+ *
+ * export function getRouter() {
+ *   return createRouter({
+ *     parseSearch: payloadParseSearch,
+ *     routeTree,
+ *     stringifySearch: payloadStringifySearch,
+ *   })
+ * }
+ * ```
+ */
+export declare const payloadParseSearch: (searchStr: string) => qs.ParsedQs;
+/**
+ * `stringifySearch` for TanStack Router's `createRouter`, required for Payload's
+ * admin UI. Pair with {@link payloadParseSearch}; see it for the full rationale.
+ */
+export declare const payloadStringifySearch: (search: Record<string, unknown>) => string;
+//# sourceMappingURL=routerSearch.d.ts.map

package/dist/utilities/routerSearch.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"routerSearch.d.ts","sourceRoot":"","sources":["../../src/utilities/routerSearch.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,MAAM,QAAQ,CAAA;AAE5B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+BG;AACH,eAAO,MAAM,kBAAkB,cAAe,MAAM,gBACS,CAAA;AAE7D;;;GAGG;AACH,eAAO,MAAM,sBAAsB,WAAY,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,WAGrE,CAAA"}

package/dist/utilities/routerSearch.js

@@ -0,0 +1,45 @@
+import * as qs from 'qs-esm';
+/**
+ * `parseSearch` for TanStack Router's `createRouter`, required for Payload's
+ * admin UI. Pair with {@link payloadStringifySearch}.
+ *
+ * Payload serializes query state (notably the list-view `where` filter) with
+ * `qs` bracket notation — e.g. `?where[or][0][and][0][x][equals]=y`. TanStack
+ * Router's default serializer treats each bracketed string as a flat key and
+ * JSON-encodes values, so it never round-trips Payload's nested query: every
+ * navigation re-encodes the already-encoded value, exponentially nesting it
+ * (`[true,"[true,\"[true…"]`) until the filter is unusable. Parsing and
+ * stringifying with `qs` (same options as `payload`/`@payloadcms/ui`) keeps
+ * the URL idempotent and the nested `where` intact across navigations.
+ *
+ * This is a router-global serializer: it applies to every route, not just
+ * `/admin`. On your own routes, search values arrive as strings (qs does no
+ * JSON type-coercion), so coerce in `validateSearch` (e.g. `Number(...)`) where
+ * you need numbers or booleans.
+ *
+ * @example
+ * ```ts
+ * import { createRouter } from '@tanstack/react-router'
+ * import { payloadParseSearch, payloadStringifySearch } from '@payloadcms/tanstack-start/shared'
+ *
+ * export function getRouter() {
+ *   return createRouter({
+ *     parseSearch: payloadParseSearch,
+ *     routeTree,
+ *     stringifySearch: payloadStringifySearch,
+ *   })
+ * }
+ * ```
+ */ export const payloadParseSearch = (searchStr)=>qs.parse(searchStr, {
+        depth: 10,
+        ignoreQueryPrefix: true
+    });
+/**
+ * `stringifySearch` for TanStack Router's `createRouter`, required for Payload's
+ * admin UI. Pair with {@link payloadParseSearch}; see it for the full rationale.
+ */ export const payloadStringifySearch = (search)=>{
+    const searchStr = qs.stringify(search);
+    return searchStr ? `?${searchStr}` : '';
+};
+
+//# sourceMappingURL=routerSearch.js.map

package/dist/utilities/routerSearch.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../src/utilities/routerSearch.ts"],"sourcesContent":["import * as qs from 'qs-esm'\n\n/**\n * `parseSearch` for TanStack Router's `createRouter`, required for Payload's\n * admin UI. Pair with {@link payloadStringifySearch}.\n *\n * Payload serializes query state (notably the list-view `where` filter) with\n * `qs` bracket notation — e.g. `?where[or][0][and][0][x][equals]=y`. TanStack\n * Router's default serializer treats each bracketed string as a flat key and\n * JSON-encodes values, so it never round-trips Payload's nested query: every\n * navigation re-encodes the already-encoded value, exponentially nesting it\n * (`[true,\"[true,\\\"[true…\"]`) until the filter is unusable. Parsing and\n * stringifying with `qs` (same options as `payload`/`@payloadcms/ui`) keeps\n * the URL idempotent and the nested `where` intact across navigations.\n *\n * This is a router-global serializer: it applies to every route, not just\n * `/admin`. On your own routes, search values arrive as strings (qs does no\n * JSON type-coercion), so coerce in `validateSearch` (e.g. `Number(...)`) where\n * you need numbers or booleans.\n *\n * @example\n * ```ts\n * import { createRouter } from '@tanstack/react-router'\n * import { payloadParseSearch, payloadStringifySearch } from '@payloadcms/tanstack-start/shared'\n *\n * export function getRouter() {\n *   return createRouter({\n *     parseSearch: payloadParseSearch,\n *     routeTree,\n *     stringifySearch: payloadStringifySearch,\n *   })\n * }\n * ```\n */\nexport const payloadParseSearch = (searchStr: string) =>\n  qs.parse(searchStr, { depth: 10, ignoreQueryPrefix: true })\n\n/**\n * `stringifySearch` for TanStack Router's `createRouter`, required for Payload's\n * admin UI. Pair with {@link payloadParseSearch}; see it for the full rationale.\n */\nexport const payloadStringifySearch = (search: Record<string, unknown>) => {\n  const searchStr = qs.stringify(search)\n  return searchStr ? `?${searchStr}` : ''\n}\n"],"names":["qs","payloadParseSearch","searchStr","parse","depth","ignoreQueryPrefix","payloadStringifySearch","search","stringify"],"mappings":"AAAA,YAAYA,QAAQ,SAAQ;AAE5B;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;CA+BC,GACD,OAAO,MAAMC,qBAAqB,CAACC,YACjCF,GAAGG,KAAK,CAACD,WAAW;QAAEE,OAAO;QAAIC,mBAAmB;IAAK,GAAE;AAE7D;;;CAGC,GACD,OAAO,MAAMC,yBAAyB,CAACC;IACrC,MAAML,YAAYF,GAAGQ,SAAS,CAACD;IAC/B,OAAOL,YAAY,CAAC,CAAC,EAAEA,WAAW,GAAG;AACvC,EAAC"}

package/dist/utilities/serverFunctionClient.d.ts

@@ -1,29 +1,8 @@
 import type { ServerFunctionClient, ServerFunctionClientArgs } from 'payload';
-/**
- * Builds the client-side `ServerFunctionClient` wired into
- * `RootProvider.serverFunction`, given the app's `createServerFn`-based
- * dispatcher (`runServerFn`).
- *
- * Strips functions / symbols / RegExps / React elements from the args before
- * dispatching: the previous `fetch + JSON.stringify` pipeline silently dropped
- * those, but TanStack Start's seroval-based wire format errors instead. We
- * mirror the relaxed behaviour so existing callers (e.g. `getFormState` in
- * `ServerFunctionsProvider`) that may pass the live form state — which can
- * carry stray functions — keep working without each call site sanitising.
- *
- * Delegates to `runServerFn`, so the response (including any RSC handles for
- * server-rendered custom components) is decoded by TanStack Start back into
- * renderable React nodes on the client.
- */
+/** Builds the admin dispatcher with native Flight response decoding. */
 export declare function createServerFunctionClient({ runServerFn, }: {
     runServerFn: (input: {
         data: ServerFunctionClientArgs;
-    }) => Promise<unknown>;
+    }) => Promise<Response>;
 }): ServerFunctionClient;
-/**
- * Recursively removes values TanStack Start's seroval wire format cannot
- * serialize (functions, symbols, RegExps, React elements, cyclic refs) and
- * normalizes `Date` subclasses to plain `Date`.
- */
-export declare function stripUnserializable(value: unknown, cache?: WeakMap<object, unknown>, ancestors?: WeakSet<object>): unknown;
 //# sourceMappingURL=serverFunctionClient.d.ts.map

package/dist/utilities/serverFunctionClient.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"serverFunctionClient.d.ts","sourceRoot":"","sources":["../../src/utilities/serverFunctionClient.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,oBAAoB,EAAE,wBAAwB,EAAE,MAAM,SAAS,CAAA;AAE7E;;;;;;;;;;;;;;;GAeG;AACH,wBAAgB,0BAA0B,CAAC,EACzC,WAAW,GACZ,EAAE;IACD,WAAW,EAAE,CAAC,KAAK,EAAE;QAAE,IAAI,EAAE,wBAAwB,CAAA;KAAE,KAAK,OAAO,CAAC,OAAO,CAAC,CAAA;CAC7E,GAAG,oBAAoB,CAKvB;AAED;;;;GAIG;AACH,wBAAgB,mBAAmB,CACjC,KAAK,EAAE,OAAO,EACd,KAAK,GAAE,OAAO,CAAC,MAAM,EAAE,OAAO,CAAiB,EAC/C,SAAS,GAAE,OAAO,CAAC,MAAM,CAAiB,GACzC,OAAO,CA4FT"}
+{"version":3,"file":"serverFunctionClient.d.ts","sourceRoot":"","sources":["../../src/utilities/serverFunctionClient.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,oBAAoB,EAAE,wBAAwB,EAAE,MAAM,SAAS,CAAA;AAE7E,wEAAwE;AACxE,wBAAgB,0BAA0B,CAAC,EACzC,WAAW,GACZ,EAAE;IACD,WAAW,EAAE,CAAC,KAAK,EAAE;QAAE,IAAI,EAAE,wBAAwB,CAAA;KAAE,KAAK,OAAO,CAAC,QAAQ,CAAC,CAAA;CAC9E,GAAG,oBAAoB,CAoBvB"}

package/dist/utilities/serverFunctionClient.js

@@ -1,109 +1,20 @@
-/**
- * Builds the client-side `ServerFunctionClient` wired into
- * `RootProvider.serverFunction`, given the app's `createServerFn`-based
- * dispatcher (`runServerFn`).
- *
- * Strips functions / symbols / RegExps / React elements from the args before
- * dispatching: the previous `fetch + JSON.stringify` pipeline silently dropped
- * those, but TanStack Start's seroval-based wire format errors instead. We
- * mirror the relaxed behaviour so existing callers (e.g. `getFormState` in
- * `ServerFunctionsProvider`) that may pass the live form state — which can
- * carry stray functions — keep working without each call site sanitising.
- *
- * Delegates to `runServerFn`, so the response (including any RSC handles for
- * server-rendered custom components) is decoded by TanStack Start back into
- * renderable React nodes on the client.
- */ export function createServerFunctionClient({ runServerFn }) {
+/** Builds the admin dispatcher with native Flight response decoding. */ export function createServerFunctionClient({ runServerFn }) {
     return async (args)=>{
-        const safeArgs = stripUnserializable(args);
-        return await runServerFn({
-            data: safeArgs
+        const response = await runServerFn({
+            data: args
         });
-    };
-}
-/**
- * Recursively removes values TanStack Start's seroval wire format cannot
- * serialize (functions, symbols, RegExps, React elements, cyclic refs) and
- * normalizes `Date` subclasses to plain `Date`.
- */ export function stripUnserializable(value, cache = new WeakMap(), ancestors = new WeakSet()) {
-    if (value === null || value === undefined) {
-        return value;
-    }
-    const t = typeof value;
-    if (t === 'function' || t === 'symbol') {
-        return undefined;
-    }
-    if (t !== 'object') {
-        return value;
-    }
-    const obj = value;
-    if (typeof obj.$$typeof === 'symbol') {
-        return undefined;
-    }
-    if (ancestors.has(obj)) {
-        return undefined;
-    }
-    if (cache.has(obj)) {
-        return cache.get(obj);
-    }
-    if (obj instanceof Date) {
-        // Normalize to a plain `Date`. Subclasses (e.g. `@date-fns/tz`'s `TZDate`,
-        // used by the schedule-publish drawer) are `instanceof Date` but have a
-        // different `constructor`, which TanStack Start's seroval serializer
-        // rejects with "The value [object Date] ... cannot be parsed/serialized".
-        return new Date(obj.getTime());
-    }
-    if (obj instanceof RegExp) {
-        return undefined;
-    }
-    ancestors.add(obj);
-    if (obj instanceof Map) {
-        const cleaned = new Map();
-        cache.set(obj, cleaned);
-        for (const [k, v] of obj){
-            const cv = stripUnserializable(v, cache, ancestors);
-            if (cv !== undefined) {
-                cleaned.set(k, cv);
-            }
+        if (!response.ok) {
+            throw new Error(`Payload server function failed with status ${response.status}`);
         }
-        ancestors.delete(obj);
-        return cleaned;
-    }
-    if (obj instanceof Set) {
-        const cleaned = new Set();
-        cache.set(obj, cleaned);
-        for (const v of obj){
-            const cv = stripUnserializable(v, cache, ancestors);
-            if (cv !== undefined) {
-                cleaned.add(cv);
-            }
+        if (response.headers.get('content-type')?.split(';')[0]?.trim() !== 'text/x-component') {
+            throw new Error('Expected a React Flight response from the Payload server function');
         }
-        ancestors.delete(obj);
-        return cleaned;
-    }
-    if (Array.isArray(obj)) {
-        const arr = [];
-        cache.set(obj, arr);
-        for (const item of obj){
-            arr.push(stripUnserializable(item, cache, ancestors));
+        if (!response.body) {
+            throw new Error('The Payload server function returned an empty Flight response');
         }
-        ancestors.delete(obj);
-        return arr;
-    }
-    if (ArrayBuffer.isView(obj)) {
-        ancestors.delete(obj);
-        return obj;
-    }
-    const result = {};
-    cache.set(obj, result);
-    for (const key of Object.keys(obj)){
-        const v = stripUnserializable(obj[key], cache, ancestors);
-        if (v !== undefined) {
-            result[key] = v;
-        }
-    }
-    ancestors.delete(obj);
-    return result;
+        const { createFromReadableStream } = await import('@tanstack/react-start/rsc');
+        return await createFromReadableStream(response.body);
+    };
 }
 
 //# sourceMappingURL=serverFunctionClient.js.map

package/dist/utilities/serverFunctionClient.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../../src/utilities/serverFunctionClient.ts"],"sourcesContent":["import type { ServerFunctionClient, ServerFunctionClientArgs } from 'payload'\n\n/**\n * Builds the client-side `ServerFunctionClient` wired into\n * `RootProvider.serverFunction`, given the app's `createServerFn`-based\n * dispatcher (`runServerFn`).\n *\n * Strips functions / symbols / RegExps / React elements from the args before\n * dispatching: the previous `fetch + JSON.stringify` pipeline silently dropped\n * those, but TanStack Start's seroval-based wire format errors instead. We\n * mirror the relaxed behaviour so existing callers (e.g. `getFormState` in\n * `ServerFunctionsProvider`) that may pass the live form state — which can\n * carry stray functions — keep working without each call site sanitising.\n *\n * Delegates to `runServerFn`, so the response (including any RSC handles for\n * server-rendered custom components) is decoded by TanStack Start back into\n * renderable React nodes on the client.\n */\nexport function createServerFunctionClient({\n  runServerFn,\n}: {\n  runServerFn: (input: { data: ServerFunctionClientArgs }) => Promise<unknown>\n}): ServerFunctionClient {\n  return (async (args: ServerFunctionClientArgs) => {\n    const safeArgs = stripUnserializable(args) as ServerFunctionClientArgs\n    return await runServerFn({ data: safeArgs })\n  }) as ServerFunctionClient\n}\n\n/**\n * Recursively removes values TanStack Start's seroval wire format cannot\n * serialize (functions, symbols, RegExps, React elements, cyclic refs) and\n * normalizes `Date` subclasses to plain `Date`.\n */\nexport function stripUnserializable(\n  value: unknown,\n  cache: WeakMap<object, unknown> = new WeakMap(),\n  ancestors: WeakSet<object> = new WeakSet(),\n): unknown {\n  if (value === null || value === undefined) {\n    return value\n  }\n\n  const t = typeof value\n  if (t === 'function' || t === 'symbol') {\n    return undefined\n  }\n  if (t !== 'object') {\n    return value\n  }\n\n  const obj = value as Record<string, unknown>\n\n  if (typeof obj.$$typeof === 'symbol') {\n    return undefined\n  }\n\n  if (ancestors.has(obj)) {\n    return undefined\n  }\n\n  if (cache.has(obj)) {\n    return cache.get(obj)\n  }\n\n  if (obj instanceof Date) {\n    // Normalize to a plain `Date`. Subclasses (e.g. `@date-fns/tz`'s `TZDate`,\n    // used by the schedule-publish drawer) are `instanceof Date` but have a\n    // different `constructor`, which TanStack Start's seroval serializer\n    // rejects with \"The value [object Date] ... cannot be parsed/serialized\".\n    return new Date(obj.getTime())\n  }\n\n  if (obj instanceof RegExp) {\n    return undefined\n  }\n\n  ancestors.add(obj)\n\n  if (obj instanceof Map) {\n    const cleaned = new Map()\n    cache.set(obj, cleaned)\n    for (const [k, v] of obj) {\n      const cv = stripUnserializable(v, cache, ancestors)\n      if (cv !== undefined) {\n        cleaned.set(k, cv)\n      }\n    }\n    ancestors.delete(obj)\n    return cleaned\n  }\n\n  if (obj instanceof Set) {\n    const cleaned = new Set()\n    cache.set(obj, cleaned)\n    for (const v of obj) {\n      const cv = stripUnserializable(v, cache, ancestors)\n      if (cv !== undefined) {\n        cleaned.add(cv)\n      }\n    }\n    ancestors.delete(obj)\n    return cleaned\n  }\n\n  if (Array.isArray(obj)) {\n    const arr: unknown[] = []\n    cache.set(obj, arr)\n    for (const item of obj) {\n      arr.push(stripUnserializable(item, cache, ancestors))\n    }\n    ancestors.delete(obj)\n    return arr\n  }\n\n  if (ArrayBuffer.isView(obj)) {\n    ancestors.delete(obj)\n    return obj\n  }\n\n  const result: Record<string, unknown> = {}\n  cache.set(obj, result)\n  for (const key of Object.keys(obj)) {\n    const v = stripUnserializable(obj[key], cache, ancestors)\n    if (v !== undefined) {\n      result[key] = v\n    }\n  }\n  ancestors.delete(obj)\n  return result\n}\n"],"names":["createServerFunctionClient","runServerFn","args","safeArgs","stripUnserializable","data","value","cache","WeakMap","ancestors","WeakSet","undefined","t","obj","$$typeof","has","get","Date","getTime","RegExp","add","Map","cleaned","set","k","v","cv","delete","Set","Array","isArray","arr","item","push","ArrayBuffer","isView","result","key","Object","keys"],"mappings":"AAEA;;;;;;;;;;;;;;;CAeC,GACD,OAAO,SAASA,2BAA2B,EACzCC,WAAW,EAGZ;IACC,OAAQ,OAAOC;QACb,MAAMC,WAAWC,oBAAoBF;QACrC,OAAO,MAAMD,YAAY;YAAEI,MAAMF;QAAS;IAC5C;AACF;AAEA;;;;CAIC,GACD,OAAO,SAASC,oBACdE,KAAc,EACdC,QAAkC,IAAIC,SAAS,EAC/CC,YAA6B,IAAIC,SAAS;IAE1C,IAAIJ,UAAU,QAAQA,UAAUK,WAAW;QACzC,OAAOL;IACT;IAEA,MAAMM,IAAI,OAAON;IACjB,IAAIM,MAAM,cAAcA,MAAM,UAAU;QACtC,OAAOD;IACT;IACA,IAAIC,MAAM,UAAU;QAClB,OAAON;IACT;IAEA,MAAMO,MAAMP;IAEZ,IAAI,OAAOO,IAAIC,QAAQ,KAAK,UAAU;QACpC,OAAOH;IACT;IAEA,IAAIF,UAAUM,GAAG,CAACF,MAAM;QACtB,OAAOF;IACT;IAEA,IAAIJ,MAAMQ,GAAG,CAACF,MAAM;QAClB,OAAON,MAAMS,GAAG,CAACH;IACnB;IAEA,IAAIA,eAAeI,MAAM;QACvB,2EAA2E;QAC3E,wEAAwE;QACxE,qEAAqE;QACrE,0EAA0E;QAC1E,OAAO,IAAIA,KAAKJ,IAAIK,OAAO;IAC7B;IAEA,IAAIL,eAAeM,QAAQ;QACzB,OAAOR;IACT;IAEAF,UAAUW,GAAG,CAACP;IAEd,IAAIA,eAAeQ,KAAK;QACtB,MAAMC,UAAU,IAAID;QACpBd,MAAMgB,GAAG,CAACV,KAAKS;QACf,KAAK,MAAM,CAACE,GAAGC,EAAE,IAAIZ,IAAK;YACxB,MAAMa,KAAKtB,oBAAoBqB,GAAGlB,OAAOE;YACzC,IAAIiB,OAAOf,WAAW;gBACpBW,QAAQC,GAAG,CAACC,GAAGE;YACjB;QACF;QACAjB,UAAUkB,MAAM,CAACd;QACjB,OAAOS;IACT;IAEA,IAAIT,eAAee,KAAK;QACtB,MAAMN,UAAU,IAAIM;QACpBrB,MAAMgB,GAAG,CAACV,KAAKS;QACf,KAAK,MAAMG,KAAKZ,IAAK;YACnB,MAAMa,KAAKtB,oBAAoBqB,GAAGlB,OAAOE;YACzC,IAAIiB,OAAOf,WAAW;gBACpBW,QAAQF,GAAG,CAACM;YACd;QACF;QACAjB,UAAUkB,MAAM,CAACd;QACjB,OAAOS;IACT;IAEA,IAAIO,MAAMC,OAAO,CAACjB,MAAM;QACtB,MAAMkB,MAAiB,EAAE;QACzBxB,MAAMgB,GAAG,CAACV,KAAKkB;QACf,KAAK,MAAMC,QAAQnB,IAAK;YACtBkB,IAAIE,IAAI,CAAC7B,oBAAoB4B,MAAMzB,OAAOE;QAC5C;QACAA,UAAUkB,MAAM,CAACd;QACjB,OAAOkB;IACT;IAEA,IAAIG,YAAYC,MAAM,CAACtB,MAAM;QAC3BJ,UAAUkB,MAAM,CAACd;QACjB,OAAOA;IACT;IAEA,MAAMuB,SAAkC,CAAC;IACzC7B,MAAMgB,GAAG,CAACV,KAAKuB;IACf,KAAK,MAAMC,OAAOC,OAAOC,IAAI,CAAC1B,KAAM;QAClC,MAAMY,IAAIrB,oBAAoBS,GAAG,CAACwB,IAAI,EAAE9B,OAAOE;QAC/C,IAAIgB,MAAMd,WAAW;YACnByB,MAAM,CAACC,IAAI,GAAGZ;QAChB;IACF;IACAhB,UAAUkB,MAAM,CAACd;IACjB,OAAOuB;AACT"}
+{"version":3,"sources":["../../src/utilities/serverFunctionClient.ts"],"sourcesContent":["import type { ServerFunctionClient, ServerFunctionClientArgs } from 'payload'\n\n/** Builds the admin dispatcher with native Flight response decoding. */\nexport function createServerFunctionClient({\n  runServerFn,\n}: {\n  runServerFn: (input: { data: ServerFunctionClientArgs }) => Promise<Response>\n}): ServerFunctionClient {\n  return (async (args: ServerFunctionClientArgs) => {\n    const response = await runServerFn({ data: args })\n\n    if (!response.ok) {\n      throw new Error(`Payload server function failed with status ${response.status}`)\n    }\n\n    if (response.headers.get('content-type')?.split(';')[0]?.trim() !== 'text/x-component') {\n      throw new Error('Expected a React Flight response from the Payload server function')\n    }\n\n    if (!response.body) {\n      throw new Error('The Payload server function returned an empty Flight response')\n    }\n\n    const { createFromReadableStream } = await import('@tanstack/react-start/rsc')\n\n    return await createFromReadableStream(response.body)\n  }) as ServerFunctionClient\n}\n"],"names":["createServerFunctionClient","runServerFn","args","response","data","ok","Error","status","headers","get","split","trim","body","createFromReadableStream"],"mappings":"AAEA,sEAAsE,GACtE,OAAO,SAASA,2BAA2B,EACzCC,WAAW,EAGZ;IACC,OAAQ,OAAOC;QACb,MAAMC,WAAW,MAAMF,YAAY;YAAEG,MAAMF;QAAK;QAEhD,IAAI,CAACC,SAASE,EAAE,EAAE;YAChB,MAAM,IAAIC,MAAM,CAAC,2CAA2C,EAAEH,SAASI,MAAM,EAAE;QACjF;QAEA,IAAIJ,SAASK,OAAO,CAACC,GAAG,CAAC,iBAAiBC,MAAM,IAAI,CAAC,EAAE,EAAEC,WAAW,oBAAoB;YACtF,MAAM,IAAIL,MAAM;QAClB;QAEA,IAAI,CAACH,SAASS,IAAI,EAAE;YAClB,MAAM,IAAIN,MAAM;QAClB;QAEA,MAAM,EAAEO,wBAAwB,EAAE,GAAG,MAAM,MAAM,CAAC;QAElD,OAAO,MAAMA,yBAAyBV,SAASS,IAAI;IACrD;AACF"}

package/dist/withPayload/config/external.d.ts

@@ -0,0 +1,34 @@
+/**
+ * Packages externalized during dev serve (`ssr.external`). Node's loader resolves
+ * their CJS/UMD directly; letting Vite's dev SSR transform touch them can break
+ * fragile UMD wrappers (e.g. `pluralize`, whose `this`-based global assignment
+ * throws when transformed rather than required).
+ *
+ * Safe here whoever declared the entry: Node resolves from the importing package,
+ * so pnpm's isolated layout never applies. The build is stricter — see
+ * {@link buildBundledPackages}.
+ */
+export declare const ssrExternalPackages: string[];
+/**
+ * Entries of {@link ssrExternalPackages} that must bundle in the production build.
+ *
+ * Externalizing only works for specifiers resolvable from the project root. These
+ * are leaf deps of Payload packages, so under pnpm they live in `.pnpm/…` and a bare
+ * specifier in a root-resolved chunk is invisible — `ERR_MODULE_NOT_FOUND` at
+ * runtime, or a build-time resolve failure under Nitro's re-bundle pass.
+ *
+ * `pluralize` also needs forcing back via `noExternal` (see `withPayload`); the
+ * storage leaves don't, since their adapters are already `noExternal`.
+ */
+export declare const buildBundledPackages: string[];
+/** Server-only package boundaries loaded directly by Node in development and production. */
+export declare const serverExternalPackages: string[];
+/** Additional installed packages that can bypass Vite's development server transforms. */
+export declare const devExternalPackages: string[];
+/**
+ * Externalizes package boundaries so packages resolve their own transitive dependencies under pnpm.
+ * Leaves that must bundle in production are excluded; see {@link buildBundledPackages}.
+ */
+export declare const buildExternalPackages: string[];
+export declare const payloadNoExternalPatterns: Array<RegExp | string>;
+//# sourceMappingURL=external.d.ts.map

package/dist/withPayload/config/external.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"external.d.ts","sourceRoot":"","sources":["../../../src/withPayload/config/external.ts"],"names":[],"mappings":"AAKA;;;;;;;;;GASG;AACH,eAAO,MAAM,mBAAmB,EAAE,MAAM,EAwBvC,CAAA;AAED;;;;;;;;;;GAUG;AACH,eAAO,MAAM,oBAAoB,EAAE,MAAM,EAOxC,CAAA;AAED,4FAA4F;AAC5F,eAAO,MAAM,sBAAsB,EAAE,MAAM,EAS1C,CAAA;AAED,0FAA0F;AAC1F,eAAO,MAAM,mBAAmB,EAAE,MAAM,EAOvC,CAAA;AAED;;;GAGG;AACH,eAAO,MAAM,qBAAqB,EAAE,MAAM,EAGzC,CAAA;AAED,eAAO,MAAM,yBAAyB,EAAE,KAAK,CAAC,MAAM,GAAG,MAAM,CAO5D,CAAA"}

package/dist/withPayload/config/external.js

@@ -0,0 +1,88 @@
+import { devServerExternalPackages as devServerExternalPayloadPackages, serverExternalPackages as serverExternalPayloadPackages } from 'payload/build-config';
+/**
+ * Packages externalized during dev serve (`ssr.external`). Node's loader resolves
+ * their CJS/UMD directly; letting Vite's dev SSR transform touch them can break
+ * fragile UMD wrappers (e.g. `pluralize`, whose `this`-based global assignment
+ * throws when transformed rather than required).
+ *
+ * Safe here whoever declared the entry: Node resolves from the importing package,
+ * so pnpm's isolated layout never applies. The build is stricter — see
+ * {@link buildBundledPackages}.
+ */ export const ssrExternalPackages = [
+    'zod',
+    'fast-uri',
+    ...serverExternalPayloadPackages,
+    'drizzle-orm',
+    'pino-pretty',
+    'nodemailer',
+    'aws4',
+    'pluralize',
+    'console-table-printer',
+    '@azure/storage-blob',
+    '@aws-sdk/client-s3',
+    '@aws-sdk/s3-request-presigner',
+    '@google-cloud/storage',
+    // Database drivers + their lazily-required companions, one group per adapter.
+    // Postgres (`@payloadcms/db-postgres`, `@payloadcms/db-vercel-postgres`)
+    'pg',
+    'pg-native',
+    'pg-cloudflare',
+    // SQLite (`@payloadcms/db-sqlite`)
+    'better-sqlite3',
+    // Mongo (`@payloadcms/db-mongodb`)
+    'mongodb',
+    'mongoose'
+];
+/**
+ * Entries of {@link ssrExternalPackages} that must bundle in the production build.
+ *
+ * Externalizing only works for specifiers resolvable from the project root. These
+ * are leaf deps of Payload packages, so under pnpm they live in `.pnpm/…` and a bare
+ * specifier in a root-resolved chunk is invisible — `ERR_MODULE_NOT_FOUND` at
+ * runtime, or a build-time resolve failure under Nitro's re-bundle pass.
+ *
+ * `pluralize` also needs forcing back via `noExternal` (see `withPayload`); the
+ * storage leaves don't, since their adapters are already `noExternal`.
+ */ export const buildBundledPackages = [
+    'pluralize',
+    // Leaf deps of the `@payloadcms/storage-*` adapters.
+    '@aws-sdk/client-s3',
+    '@aws-sdk/s3-request-presigner',
+    '@azure/storage-blob',
+    '@google-cloud/storage'
+];
+/** Server-only package boundaries loaded directly by Node in development and production. */ export const serverExternalPackages = [
+    'payload',
+    'payload/node',
+    '@payloadcms/drizzle',
+    '@payloadcms/db-mongodb',
+    '@payloadcms/db-postgres',
+    '@payloadcms/db-vercel-postgres',
+    '@payloadcms/db-sqlite',
+    '@payloadcms/db-d1-sqlite'
+];
+/** Additional installed packages that can bypass Vite's development server transforms. */ export const devExternalPackages = [
+    ...new Set([
+        // Vite otherwise transforms date-fns' full module graph during SSR.
+        'date-fns',
+        ...devServerExternalPayloadPackages,
+        ...serverExternalPackages
+    ])
+];
+/**
+ * Externalizes package boundaries so packages resolve their own transitive dependencies under pnpm.
+ * Leaves that must bundle in production are excluded; see {@link buildBundledPackages}.
+ */ export const buildExternalPackages = [
+    ...serverExternalPackages,
+    ...ssrExternalPackages.filter((pkg)=>!buildBundledPackages.includes(pkg))
+];
+export const payloadNoExternalPatterns = [
+    '@payloadcms/ui',
+    '@payloadcms/translations',
+    '@payloadcms/tanstack-start',
+    /^@payloadcms\/richtext-lexical/,
+    /^@payloadcms\/plugin-/,
+    /^@payloadcms\/storage-/
+];
+
+//# sourceMappingURL=external.js.map

package/dist/withPayload/config/external.js.map

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../src/withPayload/config/external.ts"],"sourcesContent":["import {\n  devServerExternalPackages as devServerExternalPayloadPackages,\n  serverExternalPackages as serverExternalPayloadPackages,\n} from 'payload/build-config'\n\n/**\n * Packages externalized during dev serve (`ssr.external`). Node's loader resolves\n * their CJS/UMD directly; letting Vite's dev SSR transform touch them can break\n * fragile UMD wrappers (e.g. `pluralize`, whose `this`-based global assignment\n * throws when transformed rather than required).\n *\n * Safe here whoever declared the entry: Node resolves from the importing package,\n * so pnpm's isolated layout never applies. The build is stricter — see\n * {@link buildBundledPackages}.\n */\nexport const ssrExternalPackages: string[] = [\n  'zod',\n  'fast-uri',\n  ...serverExternalPayloadPackages,\n  'drizzle-orm',\n  'pino-pretty',\n  'nodemailer',\n  'aws4',\n  'pluralize',\n  'console-table-printer',\n  '@azure/storage-blob',\n  '@aws-sdk/client-s3',\n  '@aws-sdk/s3-request-presigner',\n  '@google-cloud/storage',\n  // Database drivers + their lazily-required companions, one group per adapter.\n  // Postgres (`@payloadcms/db-postgres`, `@payloadcms/db-vercel-postgres`)\n  'pg',\n  'pg-native',\n  'pg-cloudflare',\n  // SQLite (`@payloadcms/db-sqlite`)\n  'better-sqlite3',\n  // Mongo (`@payloadcms/db-mongodb`)\n  'mongodb',\n  'mongoose',\n]\n\n/**\n * Entries of {@link ssrExternalPackages} that must bundle in the production build.\n *\n * Externalizing only works for specifiers resolvable from the project root. These\n * are leaf deps of Payload packages, so under pnpm they live in `.pnpm/…` and a bare\n * specifier in a root-resolved chunk is invisible — `ERR_MODULE_NOT_FOUND` at\n * runtime, or a build-time resolve failure under Nitro's re-bundle pass.\n *\n * `pluralize` also needs forcing back via `noExternal` (see `withPayload`); the\n * storage leaves don't, since their adapters are already `noExternal`.\n */\nexport const buildBundledPackages: string[] = [\n  'pluralize',\n  // Leaf deps of the `@payloadcms/storage-*` adapters.\n  '@aws-sdk/client-s3',\n  '@aws-sdk/s3-request-presigner',\n  '@azure/storage-blob',\n  '@google-cloud/storage',\n]\n\n/** Server-only package boundaries loaded directly by Node in development and production. */\nexport const serverExternalPackages: string[] = [\n  'payload',\n  'payload/node',\n  '@payloadcms/drizzle',\n  '@payloadcms/db-mongodb',\n  '@payloadcms/db-postgres',\n  '@payloadcms/db-vercel-postgres',\n  '@payloadcms/db-sqlite',\n  '@payloadcms/db-d1-sqlite',\n]\n\n/** Additional installed packages that can bypass Vite's development server transforms. */\nexport const devExternalPackages: string[] = [\n  ...new Set([\n    // Vite otherwise transforms date-fns' full module graph during SSR.\n    'date-fns',\n    ...devServerExternalPayloadPackages,\n    ...serverExternalPackages,\n  ]),\n]\n\n/**\n * Externalizes package boundaries so packages resolve their own transitive dependencies under pnpm.\n * Leaves that must bundle in production are excluded; see {@link buildBundledPackages}.\n */\nexport const buildExternalPackages: string[] = [\n  ...serverExternalPackages,\n  ...ssrExternalPackages.filter((pkg) => !buildBundledPackages.includes(pkg)),\n]\n\nexport const payloadNoExternalPatterns: Array<RegExp | string> = [\n  '@payloadcms/ui',\n  '@payloadcms/translations',\n  '@payloadcms/tanstack-start',\n  /^@payloadcms\\/richtext-lexical/,\n  /^@payloadcms\\/plugin-/,\n  /^@payloadcms\\/storage-/,\n]\n"],"names":["devServerExternalPackages","devServerExternalPayloadPackages","serverExternalPackages","serverExternalPayloadPackages","ssrExternalPackages","buildBundledPackages","devExternalPackages","Set","buildExternalPackages","filter","pkg","includes","payloadNoExternalPatterns"],"mappings":"AAAA,SACEA,6BAA6BC,gCAAgC,EAC7DC,0BAA0BC,6BAA6B,QAClD,uBAAsB;AAE7B;;;;;;;;;CASC,GACD,OAAO,MAAMC,sBAAgC;IAC3C;IACA;OACGD;IACH;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA,8EAA8E;IAC9E,yEAAyE;IACzE;IACA;IACA;IACA,mCAAmC;IACnC;IACA,mCAAmC;IACnC;IACA;CACD,CAAA;AAED;;;;;;;;;;CAUC,GACD,OAAO,MAAME,uBAAiC;IAC5C;IACA,qDAAqD;IACrD;IACA;IACA;IACA;CACD,CAAA;AAED,0FAA0F,GAC1F,OAAO,MAAMH,yBAAmC;IAC9C;IACA;IACA;IACA;IACA;IACA;IACA;IACA;CACD,CAAA;AAED,wFAAwF,GACxF,OAAO,MAAMI,sBAAgC;OACxC,IAAIC,IAAI;QACT,oEAAoE;QACpE;WACGN;WACAC;KACJ;CACF,CAAA;AAED;;;CAGC,GACD,OAAO,MAAMM,wBAAkC;OAC1CN;OACAE,oBAAoBK,MAAM,CAAC,CAACC,MAAQ,CAACL,qBAAqBM,QAAQ,CAACD;CACvE,CAAA;AAED,OAAO,MAAME,4BAAoD;IAC/D;IACA;IACA;IACA;IACA;IACA;CACD,CAAA"}

package/dist/withPayload/config/optimizeDeps.d.ts

@@ -0,0 +1,25 @@
+/**
+ * Client dep-optimizer config used by `withPayload`. Kept separate from the
+ * SSR/RSC externalization config (`./external.ts`) so each concern stays small.
+ */
+/**
+ * Packages we know contain Node-only code or top-level side effects requiring
+ * Node APIs. Excluding them from the client optimizer prevents Vite from
+ * walking into their main entries and trying to bundle server-only imports
+ * for the browser.
+ */
+export declare const optimizeDepsExcludeDefaults: string[];
+/**
+ * Transitive dependencies of `@payloadcms/ui` and `payload` that need to be
+ * pre-bundled for the client. Vite's auto-discovery doesn't reliably pick
+ * these up because their parent packages are in `optimizeDeps.exclude`, so we
+ * list them explicitly using the `parent > child` syntax.
+ *
+ * Each entry below fixes a specific late-discovery re-optimization: without it,
+ * Vite discovers the dep *after* its initial crawl, forcing a full dep
+ * re-optimization mid-session that 404s in-flight `.vite/deps/*` chunks and
+ * remounts the admin (dropping client state). This is why the list can't simply
+ * be deleted — it is the "complete first pass" for the admin's dep graph.
+ */
+export declare const optimizeDepsIncludeDefaults: string[];
+//# sourceMappingURL=optimizeDeps.d.ts.map

package/dist/withPayload/config/optimizeDeps.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"optimizeDeps.d.ts","sourceRoot":"","sources":["../../../src/withPayload/config/optimizeDeps.ts"],"names":[],"mappings":"AAAA;;;GAGG;AAEH;;;;;GAKG;AACH,eAAO,MAAM,2BAA2B,EAAE,MAAM,EA0D/C,CAAA;AAED;;;;;;;;;;;GAWG;AACH,eAAO,MAAM,2BAA2B,EAAE,MAAM,EA+E/C,CAAA"}

package/dist/{vite/constants.js → withPayload/config/optimizeDeps.js}

@@ -1,67 +1,7 @@
 /**
- * Vite-level configuration constants used by `payloadPlugin`. Kept separate so
- * `plugin.ts` stays focused on wiring.
+ * Client dep-optimizer config used by `withPayload`. Kept separate from the
+ * SSR/RSC externalization config (`./external.ts`) so each concern stays small.
  */ /**
- * Server-only packages (Node-only or only ever used by the server bundle).
- * These are the Vite equivalent of Next.js's `serverExternalPackages`.
- */ export const ssrExternalPackages = [
-    'ajv',
-    'fast-uri',
-    'drizzle-kit',
-    'drizzle-kit/api',
-    'drizzle-orm',
-    'sharp',
-    'libsql',
-    'require-in-the-middle',
-    'json-schema-to-typescript',
-    'pino',
-    'pino-pretty',
-    'graphql',
-    'mongodb',
-    'mongoose',
-    'better-sqlite3',
-    'pg',
-    'pg-native',
-    'nodemailer',
-    'aws4',
-    'pluralize',
-    'console-table-printer',
-    '@azure/storage-blob',
-    '@aws-sdk/client-s3',
-    '@aws-sdk/s3-request-presigner',
-    '@google-cloud/storage'
-];
-/**
- * Payload packages whose source must be processed by Vite even on the server
- * (because they are workspace `.ts` files in dev). Server-only adapters
- * (`@payloadcms/db-*`, `@payloadcms/email-*`, `@payloadcms/next`, etc.) are
- * intentionally not included — those should stay external on the SSR side.
- */ export const payloadNoExternalPatterns = [
-    '@payloadcms/ui',
-    '@payloadcms/translations',
-    '@payloadcms/tanstack-start',
-    /^@payloadcms\/richtext-lexical/,
-    /^@payloadcms\/plugin-/,
-    /^@payloadcms\/storage-/
-];
-/**
- * The subset of `payloadNoExternalPatterns` that needs to participate in the
- * RSC environment. Plugins and storage adapters must be included: they register
- * custom providers/components (e.g. `plugin-multi-tenant`'s `'use client'`
- * `TenantSelectionProvider`) that render in the RSC graph via
- * `RenderServerComponent`. If the package stays external to RSC, `plugin-rsc`
- * never transforms its `'use client'` modules into client references, so the
- * component executes server-side and crashes on the first hook
- * (`Cannot read properties of null (reading 'useState')`).
- */ export const payloadRscNoExternalPatterns = [
-    '@payloadcms/ui',
-    '@payloadcms/translations',
-    '@payloadcms/tanstack-start',
-    /^@payloadcms\/richtext-lexical/,
-    /^@payloadcms\/plugin-/,
-    /^@payloadcms\/storage-/
-];
-/**
  * Packages we know contain Node-only code or top-level side effects requiring
  * Node APIs. Excluding them from the client optimizer prevents Vite from
  * walking into their main entries and trying to bundle server-only imports
@@ -85,15 +25,57 @@
     // server-only APIs (e.g. `BlobSASPermissions`), which crashes the dev
     // server with a `MISSING_EXPORT` error before any test runs.
     '@azure/storage-blob',
+    // Preserve RSC client boundaries on storage admin upload handlers.
+    '@payloadcms/storage-azure',
+    '@payloadcms/storage-r2',
+    '@payloadcms/storage-vercel-blob',
     '@aws-sdk/client-s3',
     '@aws-sdk/s3-request-presigner',
-    '@google-cloud/storage'
+    '@google-cloud/storage',
+    // Packages whose admin component barrel re-exports `'use client'` modules
+    // without carrying the directive itself. Pre-bundling one puts those modules
+    // in the optimized dep chunk *and* in the `rsc` environment as client
+    // references, which `@vitejs/plugin-rsc` warns about ("client component
+    // dependency is inconsistently optimized") once per component. Barrels that
+    // start with `'use client'` (e.g. `richtext-lexical`, `plugin-stripe`) don't
+    // warn and stay pre-bundled. Only shows up in published installs; workspace
+    // source is never pre-bundled.
+    '@payloadcms/plugin-cloud-storage',
+    '@payloadcms/plugin-ecommerce',
+    '@payloadcms/plugin-form-builder',
+    '@payloadcms/plugin-import-export',
+    '@payloadcms/plugin-multi-tenant',
+    '@payloadcms/plugin-search',
+    '@payloadcms/plugin-sentry',
+    '@payloadcms/plugin-seo',
+    // Database adapters and their drivers. The client scan reaches them through the
+    // Payload config (it follows server functions' `import('@payload-config')`
+    // without TanStack's server-fn stripping), so Vite would pre-bundle the whole
+    // driver for a browser that never loads it. Mongoose 9 has no browser build, so
+    // that bundles `mongodb`, whose optional `@aws-sdk/credential-providers` peer —
+    // when linked, as in the monorepo via `@payloadcms/payload-cloud` — fails the
+    // same `MISSING_EXPORT` way. Published installs reach the adapter packages;
+    // the monorepo, which resolves them to source, reaches the drivers.
+    '@payloadcms/db-d1-sqlite',
+    '@payloadcms/db-mongodb',
+    '@payloadcms/db-postgres',
+    '@payloadcms/db-sqlite',
+    '@payloadcms/db-vercel-postgres',
+    '@payloadcms/drizzle',
+    'mongodb',
+    'mongoose'
 ];
 /**
  * Transitive dependencies of `@payloadcms/ui` and `payload` that need to be
  * pre-bundled for the client. Vite's auto-discovery doesn't reliably pick
  * these up because their parent packages are in `optimizeDeps.exclude`, so we
  * list them explicitly using the `parent > child` syntax.
+ *
+ * Each entry below fixes a specific late-discovery re-optimization: without it,
+ * Vite discovers the dep *after* its initial crawl, forcing a full dep
+ * re-optimization mid-session that 404s in-flight `.vite/deps/*` chunks and
+ * remounts the admin (dropping client state). This is why the list can't simply
+ * be deleted — it is the "complete first pass" for the admin's dep graph.
  */ export const optimizeDepsIncludeDefaults = [
     '@payloadcms/ui > sonner',
     '@payloadcms/ui > @faceless-ui/modal',
@@ -145,16 +127,16 @@
     '@payloadcms/ui > react-select > prop-types > react-is',
     '@payloadcms/ui > date-fns/locale/en-US',
     // Further late discoveries observed re-optimizing mid-run in CI cold starts
-    // (see CI logs: "✨ new dependencies optimized: @dnd-kit/modifiers / ajv /
+    // (see CI logs: "✨ new dependencies optimized: @dnd-kit/modifiers / zod /
     // dequal/lite"). The modular dashboard pulls in `@dnd-kit/modifiers` on first
     // render; form-state diffing reaches `dequal/lite` (a distinct entry point
     // from the already-listed `dequal`); client-side field validation reaches
-    // `ajv` *through `payload`* — it is `ssrExternal` server-side but still
+    // `zod` *through `payload`* — it is `ssrExternal` server-side but still
     // bundled into the client, and must be pathed via `payload` so the optimizer
     // pre-bundles the exact copy the runtime loads.
     '@payloadcms/ui > @dnd-kit/modifiers',
     '@payloadcms/ui > dequal/lite',
-    'payload > ajv',
+    'payload > zod',
     // The storage client-upload suites (esp. vercel-blob) crawl part of the
     // `payload` server runtime into the client bundle and discover these late,
     // triggering several "optimized dependencies changed. reloading" waves that
@@ -167,11 +149,12 @@
     'payload > path-to-regexp',
     'payload > console-table-printer',
     'payload > ci-info',
-    'payload > image-size',
-    'payload > image-size/fromFile',
+    'payload > image-dimensions',
     'payload > ipaddr.js',
     'payload > range-parser',
-    'payload > sanitize-filename'
+    'payload > sanitize-filename',
+    // `@azure/storage-blob` is excluded, so pre-bundle its CommonJS browser dependency explicitly.
+    '@azure/storage-blob > events'
 ];
 
-//# sourceMappingURL=constants.js.map
+//# sourceMappingURL=optimizeDeps.js.map