@payloadcms/tanstack-start 4.0.0-internal.a0ef1b8 → 4.0.0-internal.a2d053c

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

@@ -0,0 +1,8 @@
+import type { ServerFunctionClient, ServerFunctionClientArgs } from 'payload';
+/** Builds the admin dispatcher with native Flight response decoding. */
+export declare function createServerFunctionClient({ runServerFn, }: {
+    runServerFn: (input: {
+        data: ServerFunctionClientArgs;
+    }) => Promise<Response>;
+}): ServerFunctionClient;
+//# sourceMappingURL=serverFunctionClient.d.ts.map

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

@@ -0,0 +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,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

@@ -0,0 +1,20 @@
+/** Builds the admin dispatcher with native Flight response decoding. */ export function createServerFunctionClient({ runServerFn }) {
+    return async (args)=>{
+        const response = await runServerFn({
+            data: args
+        });
+        if (!response.ok) {
+            throw new Error(`Payload server function failed with status ${response.status}`);
+        }
+        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');
+        }
+        if (!response.body) {
+            throw new Error('The Payload server function returned an empty Flight response');
+        }
+        const { createFromReadableStream } = await import('@tanstack/react-start/rsc');
+        return await createFromReadableStream(response.body);
+    };
+}
+
+//# sourceMappingURL=serverFunctionClient.js.map

package/dist/utilities/serverFunctionClient.js.map

@@ -0,0 +1 @@
+{"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/withPayload/config/optimizeDeps.js

@@ -0,0 +1,160 @@
+/**
+ * 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 const optimizeDepsExcludeDefaults = [
+    'sharp',
+    '@payloadcms/ui',
+    '@payloadcms/tanstack-start',
+    'payload',
+    'pino',
+    'pino-pretty',
+    'busboy',
+    'get-tsconfig',
+    'ws',
+    'croner',
+    'prompts',
+    'file-type',
+    // Server-only SDKs used by `@payloadcms/storage-*` adapters. Vite
+    // sometimes walks these from the main package entry while scanning
+    // workspace deps, and the browser sub-bundles do not expose the
+    // 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',
+    // 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',
+    '@payloadcms/ui > @faceless-ui/window-info',
+    '@payloadcms/ui > @faceless-ui/scroll-info',
+    '@payloadcms/ui > @dnd-kit/core',
+    '@payloadcms/ui > @dnd-kit/sortable',
+    '@payloadcms/ui > @dnd-kit/utilities',
+    '@payloadcms/ui > react-datepicker',
+    '@payloadcms/ui > react-select',
+    '@payloadcms/ui > react-select/creatable',
+    '@payloadcms/ui > react-image-crop',
+    '@payloadcms/ui > @monaco-editor/react',
+    '@payloadcms/ui > date-fns',
+    '@payloadcms/ui > date-fns/transpose',
+    '@payloadcms/ui > @date-fns/tz/date/mini',
+    '@payloadcms/ui > uuid',
+    '@payloadcms/ui > use-context-selector',
+    '@payloadcms/ui > bson-objectid',
+    '@payloadcms/ui > dequal',
+    '@payloadcms/ui > object-to-formdata',
+    '@payloadcms/ui > md5',
+    'payload > deepmerge',
+    'payload > pluralize',
+    // `scheduler` is a transitive dep of `react-dom`, not a direct dependency of
+    // the app, so a bare `'scheduler'` specifier fails to resolve from an isolated
+    // install (`test/node_modules` built with `pnpm i --ignore-workspace`), where
+    // it isn't hoisted to the top level. Path it through `react-dom` so the
+    // optimizer resolves the exact copy the runtime loads.
+    'react-dom > scheduler',
+    // `@payloadcms/ui` (in `optimizeDeps.exclude`) ships compiled output that the
+    // React Compiler rewrote to `import { c } from 'react/compiler-runtime'`.
+    // Because its parent is excluded, the optimizer never crawls in to discover
+    // this entry, so Vite serves `react/compiler-runtime` raw. That file is
+    // CommonJS (`module.exports = require(...)`), so the named `c` export can't be
+    // statically extracted and every client component throws "does not provide an
+    // export named 'c'". Pre-bundling it lets esbuild synthesize the named export.
+    'react/compiler-runtime',
+    // Transitive deps that Vite otherwise discovers *after* the initial crawl
+    // (react-select pulls in @floating-ui at runtime; react-is is reached via
+    // react-transition-group/prop-types; the default date-fns locale is loaded
+    // through a dynamic `date-fns/locale/${key}` import). A late discovery forces
+    // a full dep re-optimization mid-session, which 404s every in-flight
+    // `.vite/deps/*` chunk ("Pre-transform error: file does not exist in the
+    // optimize deps directory") and breaks the admin UI in CI cold starts.
+    // Pre-bundling them keeps the first optimization pass complete.
+    '@payloadcms/ui > react-select > @floating-ui/dom',
+    '@payloadcms/ui > react-select > @floating-ui/dom > @floating-ui/core',
+    '@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 / 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
+    // `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 > 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
+    // reload the page mid-test (the bulk-upload drawer's Create New button /
+    // dropzone vanish and the direct-to-bucket PUT never fires). Pre-bundle the
+    // whole observed set so the first pass is complete.
+    'payload > undici',
+    'payload > jose',
+    'payload > dataloader',
+    'payload > path-to-regexp',
+    'payload > console-table-printer',
+    'payload > ci-info',
+    'payload > image-dimensions',
+    'payload > ipaddr.js',
+    'payload > range-parser',
+    'payload > sanitize-filename',
+    // `@azure/storage-blob` is excluded, so pre-bundle its CommonJS browser dependency explicitly.
+    '@azure/storage-blob > events'
+];
+
+//# sourceMappingURL=optimizeDeps.js.map

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

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../src/withPayload/config/optimizeDeps.ts"],"sourcesContent":["/**\n * Client dep-optimizer config used by `withPayload`. Kept separate from the\n * SSR/RSC externalization config (`./external.ts`) so each concern stays small.\n */\n\n/**\n * Packages we know contain Node-only code or top-level side effects requiring\n * Node APIs. Excluding them from the client optimizer prevents Vite from\n * walking into their main entries and trying to bundle server-only imports\n * for the browser.\n */\nexport const optimizeDepsExcludeDefaults: string[] = [\n  'sharp',\n  '@payloadcms/ui',\n  '@payloadcms/tanstack-start',\n  'payload',\n  'pino',\n  'pino-pretty',\n  'busboy',\n  'get-tsconfig',\n  'ws',\n  'croner',\n  'prompts',\n  'file-type',\n  // Server-only SDKs used by `@payloadcms/storage-*` adapters. Vite\n  // sometimes walks these from the main package entry while scanning\n  // workspace deps, and the browser sub-bundles do not expose the\n  // server-only APIs (e.g. `BlobSASPermissions`), which crashes the dev\n  // server with a `MISSING_EXPORT` error before any test runs.\n  '@azure/storage-blob',\n  // Preserve RSC client boundaries on storage admin upload handlers.\n  '@payloadcms/storage-azure',\n  '@payloadcms/storage-r2',\n  '@payloadcms/storage-vercel-blob',\n  '@aws-sdk/client-s3',\n  '@aws-sdk/s3-request-presigner',\n  '@google-cloud/storage',\n  // Packages whose admin component barrel re-exports `'use client'` modules\n  // without carrying the directive itself. Pre-bundling one puts those modules\n  // in the optimized dep chunk *and* in the `rsc` environment as client\n  // references, which `@vitejs/plugin-rsc` warns about (\"client component\n  // dependency is inconsistently optimized\") once per component. Barrels that\n  // start with `'use client'` (e.g. `richtext-lexical`, `plugin-stripe`) don't\n  // warn and stay pre-bundled. Only shows up in published installs; workspace\n  // source is never pre-bundled.\n  '@payloadcms/plugin-cloud-storage',\n  '@payloadcms/plugin-ecommerce',\n  '@payloadcms/plugin-form-builder',\n  '@payloadcms/plugin-import-export',\n  '@payloadcms/plugin-multi-tenant',\n  '@payloadcms/plugin-search',\n  '@payloadcms/plugin-sentry',\n  '@payloadcms/plugin-seo',\n  // Database adapters and their drivers. The client scan reaches them through the\n  // Payload config (it follows server functions' `import('@payload-config')`\n  // without TanStack's server-fn stripping), so Vite would pre-bundle the whole\n  // driver for a browser that never loads it. Mongoose 9 has no browser build, so\n  // that bundles `mongodb`, whose optional `@aws-sdk/credential-providers` peer —\n  // when linked, as in the monorepo via `@payloadcms/payload-cloud` — fails the\n  // same `MISSING_EXPORT` way. Published installs reach the adapter packages;\n  // the monorepo, which resolves them to source, reaches the drivers.\n  '@payloadcms/db-d1-sqlite',\n  '@payloadcms/db-mongodb',\n  '@payloadcms/db-postgres',\n  '@payloadcms/db-sqlite',\n  '@payloadcms/db-vercel-postgres',\n  '@payloadcms/drizzle',\n  'mongodb',\n  'mongoose',\n]\n\n/**\n * Transitive dependencies of `@payloadcms/ui` and `payload` that need to be\n * pre-bundled for the client. Vite's auto-discovery doesn't reliably pick\n * these up because their parent packages are in `optimizeDeps.exclude`, so we\n * list them explicitly using the `parent > child` syntax.\n *\n * Each entry below fixes a specific late-discovery re-optimization: without it,\n * Vite discovers the dep *after* its initial crawl, forcing a full dep\n * re-optimization mid-session that 404s in-flight `.vite/deps/*` chunks and\n * remounts the admin (dropping client state). This is why the list can't simply\n * be deleted — it is the \"complete first pass\" for the admin's dep graph.\n */\nexport const optimizeDepsIncludeDefaults: string[] = [\n  '@payloadcms/ui > sonner',\n  '@payloadcms/ui > @faceless-ui/modal',\n  '@payloadcms/ui > @faceless-ui/window-info',\n  '@payloadcms/ui > @faceless-ui/scroll-info',\n  '@payloadcms/ui > @dnd-kit/core',\n  '@payloadcms/ui > @dnd-kit/sortable',\n  '@payloadcms/ui > @dnd-kit/utilities',\n  '@payloadcms/ui > react-datepicker',\n  '@payloadcms/ui > react-select',\n  '@payloadcms/ui > react-select/creatable',\n  '@payloadcms/ui > react-image-crop',\n  '@payloadcms/ui > @monaco-editor/react',\n  '@payloadcms/ui > date-fns',\n  '@payloadcms/ui > date-fns/transpose',\n  '@payloadcms/ui > @date-fns/tz/date/mini',\n  '@payloadcms/ui > uuid',\n  '@payloadcms/ui > use-context-selector',\n  '@payloadcms/ui > bson-objectid',\n  '@payloadcms/ui > dequal',\n  '@payloadcms/ui > object-to-formdata',\n  '@payloadcms/ui > md5',\n  'payload > deepmerge',\n  'payload > pluralize',\n  // `scheduler` is a transitive dep of `react-dom`, not a direct dependency of\n  // the app, so a bare `'scheduler'` specifier fails to resolve from an isolated\n  // install (`test/node_modules` built with `pnpm i --ignore-workspace`), where\n  // it isn't hoisted to the top level. Path it through `react-dom` so the\n  // optimizer resolves the exact copy the runtime loads.\n  'react-dom > scheduler',\n  // `@payloadcms/ui` (in `optimizeDeps.exclude`) ships compiled output that the\n  // React Compiler rewrote to `import { c } from 'react/compiler-runtime'`.\n  // Because its parent is excluded, the optimizer never crawls in to discover\n  // this entry, so Vite serves `react/compiler-runtime` raw. That file is\n  // CommonJS (`module.exports = require(...)`), so the named `c` export can't be\n  // statically extracted and every client component throws \"does not provide an\n  // export named 'c'\". Pre-bundling it lets esbuild synthesize the named export.\n  'react/compiler-runtime',\n  // Transitive deps that Vite otherwise discovers *after* the initial crawl\n  // (react-select pulls in @floating-ui at runtime; react-is is reached via\n  // react-transition-group/prop-types; the default date-fns locale is loaded\n  // through a dynamic `date-fns/locale/${key}` import). A late discovery forces\n  // a full dep re-optimization mid-session, which 404s every in-flight\n  // `.vite/deps/*` chunk (\"Pre-transform error: file does not exist in the\n  // optimize deps directory\") and breaks the admin UI in CI cold starts.\n  // Pre-bundling them keeps the first optimization pass complete.\n  '@payloadcms/ui > react-select > @floating-ui/dom',\n  '@payloadcms/ui > react-select > @floating-ui/dom > @floating-ui/core',\n  '@payloadcms/ui > react-select > prop-types > react-is',\n  '@payloadcms/ui > date-fns/locale/en-US',\n  // Further late discoveries observed re-optimizing mid-run in CI cold starts\n  // (see CI logs: \"✨ new dependencies optimized: @dnd-kit/modifiers / zod /\n  // dequal/lite\"). The modular dashboard pulls in `@dnd-kit/modifiers` on first\n  // render; form-state diffing reaches `dequal/lite` (a distinct entry point\n  // from the already-listed `dequal`); client-side field validation reaches\n  // `zod` *through `payload`* — it is `ssrExternal` server-side but still\n  // bundled into the client, and must be pathed via `payload` so the optimizer\n  // pre-bundles the exact copy the runtime loads.\n  '@payloadcms/ui > @dnd-kit/modifiers',\n  '@payloadcms/ui > dequal/lite',\n  'payload > zod',\n  // The storage client-upload suites (esp. vercel-blob) crawl part of the\n  // `payload` server runtime into the client bundle and discover these late,\n  // triggering several \"optimized dependencies changed. reloading\" waves that\n  // reload the page mid-test (the bulk-upload drawer's Create New button /\n  // dropzone vanish and the direct-to-bucket PUT never fires). Pre-bundle the\n  // whole observed set so the first pass is complete.\n  'payload > undici',\n  'payload > jose',\n  'payload > dataloader',\n  'payload > path-to-regexp',\n  'payload > console-table-printer',\n  'payload > ci-info',\n  'payload > image-dimensions',\n  'payload > ipaddr.js',\n  'payload > range-parser',\n  'payload > sanitize-filename',\n  // `@azure/storage-blob` is excluded, so pre-bundle its CommonJS browser dependency explicitly.\n  '@azure/storage-blob > events',\n]\n"],"names":["optimizeDepsExcludeDefaults","optimizeDepsIncludeDefaults"],"mappings":"AAAA;;;CAGC,GAED;;;;;CAKC,GACD,OAAO,MAAMA,8BAAwC;IACnD;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA,kEAAkE;IAClE,mEAAmE;IACnE,gEAAgE;IAChE,sEAAsE;IACtE,6DAA6D;IAC7D;IACA,mEAAmE;IACnE;IACA;IACA;IACA;IACA;IACA;IACA,0EAA0E;IAC1E,6EAA6E;IAC7E,sEAAsE;IACtE,wEAAwE;IACxE,4EAA4E;IAC5E,6EAA6E;IAC7E,4EAA4E;IAC5E,+BAA+B;IAC/B;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA,gFAAgF;IAChF,2EAA2E;IAC3E,8EAA8E;IAC9E,gFAAgF;IAChF,gFAAgF;IAChF,8EAA8E;IAC9E,4EAA4E;IAC5E,oEAAoE;IACpE;IACA;IACA;IACA;IACA;IACA;IACA;IACA;CACD,CAAA;AAED;;;;;;;;;;;CAWC,GACD,OAAO,MAAMC,8BAAwC;IACnD;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA,6EAA6E;IAC7E,+EAA+E;IAC/E,8EAA8E;IAC9E,wEAAwE;IACxE,uDAAuD;IACvD;IACA,8EAA8E;IAC9E,0EAA0E;IAC1E,4EAA4E;IAC5E,wEAAwE;IACxE,+EAA+E;IAC/E,8EAA8E;IAC9E,+EAA+E;IAC/E;IACA,0EAA0E;IAC1E,0EAA0E;IAC1E,2EAA2E;IAC3E,8EAA8E;IAC9E,qEAAqE;IACrE,yEAAyE;IACzE,uEAAuE;IACvE,gEAAgE;IAChE;IACA;IACA;IACA;IACA,4EAA4E;IAC5E,0EAA0E;IAC1E,8EAA8E;IAC9E,2EAA2E;IAC3E,0EAA0E;IAC1E,wEAAwE;IACxE,6EAA6E;IAC7E,gDAAgD;IAChD;IACA;IACA;IACA,wEAAwE;IACxE,2EAA2E;IAC3E,4EAA4E;IAC5E,yEAAyE;IACzE,4EAA4E;IAC5E,oDAAoD;IACpD;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA;IACA,+FAA+F;IAC/F;CACD,CAAA"}

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

@@ -0,0 +1,14 @@
+/**
+ * SCSS `@import`/`@use` importers applied for every Payload consumer.
+ *
+ * Resolves webpack-style `~@payloadcms/...` tilde specifiers (emitted by
+ * first-party Payload package styles, e.g. `@payloadcms/richtext-slate`) to the
+ * installed package via Node resolution. Because it goes through the package's
+ * `exports` map, it picks the workspace `src` scss in the monorepo and the
+ * published `dist` scss in a consumer install automatically — no per-app
+ * `findFileUrl` shim needed.
+ */
+export declare const payloadScssImporters: {
+    findFileUrl(url: string): null | URL;
+}[];
+//# sourceMappingURL=scss.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"scss.d.ts","sourceRoot":"","sources":["../../../src/withPayload/config/scss.ts"],"names":[],"mappings":"AAKA;;;;;;;;;GASG;AACH,eAAO,MAAM,oBAAoB;qBAEZ,MAAM,GAAG,IAAI,GAAG,GAAG;GAWvC,CAAA"}

package/dist/withPayload/config/scss.js

@@ -0,0 +1,28 @@
+import { createRequire } from 'node:module';
+import { pathToFileURL } from 'node:url';
+const require = createRequire(import.meta.url);
+/**
+ * SCSS `@import`/`@use` importers applied for every Payload consumer.
+ *
+ * Resolves webpack-style `~@payloadcms/...` tilde specifiers (emitted by
+ * first-party Payload package styles, e.g. `@payloadcms/richtext-slate`) to the
+ * installed package via Node resolution. Because it goes through the package's
+ * `exports` map, it picks the workspace `src` scss in the monorepo and the
+ * published `dist` scss in a consumer install automatically — no per-app
+ * `findFileUrl` shim needed.
+ */ export const payloadScssImporters = [
+    {
+        findFileUrl (url) {
+            if (!url.startsWith('~@payloadcms/')) {
+                return null;
+            }
+            try {
+                return pathToFileURL(require.resolve(url.slice(1)));
+            } catch  {
+                return null;
+            }
+        }
+    }
+];
+
+//# sourceMappingURL=scss.js.map

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

@@ -0,0 +1 @@
+{"version":3,"sources":["../../../src/withPayload/config/scss.ts"],"sourcesContent":["import { createRequire } from 'node:module'\nimport { pathToFileURL } from 'node:url'\n\nconst require = createRequire(import.meta.url)\n\n/**\n * SCSS `@import`/`@use` importers applied for every Payload consumer.\n *\n * Resolves webpack-style `~@payloadcms/...` tilde specifiers (emitted by\n * first-party Payload package styles, e.g. `@payloadcms/richtext-slate`) to the\n * installed package via Node resolution. Because it goes through the package's\n * `exports` map, it picks the workspace `src` scss in the monorepo and the\n * published `dist` scss in a consumer install automatically — no per-app\n * `findFileUrl` shim needed.\n */\nexport const payloadScssImporters = [\n  {\n    findFileUrl(url: string): null | URL {\n      if (!url.startsWith('~@payloadcms/')) {\n        return null\n      }\n      try {\n        return pathToFileURL(require.resolve(url.slice(1)))\n      } catch {\n        return null\n      }\n    },\n  },\n]\n"],"names":["createRequire","pathToFileURL","require","url","payloadScssImporters","findFileUrl","startsWith","resolve","slice"],"mappings":"AAAA,SAASA,aAAa,QAAQ,cAAa;AAC3C,SAASC,aAAa,QAAQ,WAAU;AAExC,MAAMC,UAAUF,cAAc,YAAYG,GAAG;AAE7C;;;;;;;;;CASC,GACD,OAAO,MAAMC,uBAAuB;IAClC;QACEC,aAAYF,GAAW;YACrB,IAAI,CAACA,IAAIG,UAAU,CAAC,kBAAkB;gBACpC,OAAO;YACT;YACA,IAAI;gBACF,OAAOL,cAAcC,QAAQK,OAAO,CAACJ,IAAIK,KAAK,CAAC;YACjD,EAAE,OAAM;gBACN,OAAO;YACT;QACF;IACF;CACD,CAAA"}

package/dist/withPayload/devConfigReload.d.ts

@@ -0,0 +1,14 @@
+import type { PluginOption } from 'vite';
+/**
+ * Reloads Payload when `payload.config.ts`, or anything it imports, changes.
+ *
+ * Vite re-evaluates the config module on its own, but `getPayload` keeps
+ * serving its cached instance until a `DevReloadStrategy` marks it stale. This
+ * plugin only broadcasts the change; `devConfigReload.server.ts` subscribes
+ * from inside the server runtime and marks the instance, which `getPayload`
+ * then reloads on its next call.
+ */
+export declare function payloadDevConfigReload({ payloadConfigPath, }: {
+    payloadConfigPath: string;
+}): PluginOption;
+//# sourceMappingURL=devConfigReload.d.ts.map

package/dist/withPayload/devConfigReload.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"devConfigReload.d.ts","sourceRoot":"","sources":["../../src/withPayload/devConfigReload.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAyB,YAAY,EAAiB,MAAM,MAAM,CAAA;AAO9E;;;;;;;;GAQG;AACH,wBAAgB,sBAAsB,CAAC,EACrC,iBAAiB,GAClB,EAAE;IACD,iBAAiB,EAAE,MAAM,CAAA;CAC1B,GAAG,YAAY,CA+Cf"}