@payloadcms/next 3.68.0-internal-debug.e9b66ee → 3.68.0-internal.10bf491

package/dist/withPayload.js

@@ -1,229 +1,155 @@
+/* eslint-disable no-console */ /* eslint-disable no-restricted-exports */import { getNextjsVersion, supportsTurbopackExternalizeTransitiveDependencies } from './withPayload.utils.js';
+import { withPayloadLegacy } from './withPayloadLegacy.js';
+const poweredByHeader = {
+  key: 'X-Powered-By',
+  value: 'Next.js, Payload'
+};
 /**
  * @param {import('next').NextConfig} nextConfig
  * @param {Object} [options] - Optional configuration options
  * @param {boolean} [options.devBundleServerPackages] - Whether to bundle server packages in development mode. @default false
- *
- * @returns {import('next').NextConfig}
- * */ export const withPayload = (nextConfig = {}, options = {})=>{
-    const env = nextConfig.env || {};
-    if (nextConfig.experimental?.staleTimes?.dynamic) {
-        console.warn('Payload detected a non-zero value for the `staleTimes.dynamic` option in your Next.js config. This will slow down page transitions and may cause stale data to load within the Admin panel. To clear this warning, remove the `staleTimes.dynamic` option from your Next.js config or set it to 0. In the future, Next.js may support scoping this option to specific routes.');
-        env.NEXT_PUBLIC_ENABLE_ROUTER_CACHE_REFRESH = 'true';
-    }
-    if (process.env.PAYLOAD_PATCH_TURBOPACK_WARNINGS !== 'false') {
-        // TODO: This warning is thrown because we cannot externalize the entry-point package for client-s3, so we patch the warning to not show it.
-        // We can remove this once Next.js implements https://github.com/vercel/next.js/discussions/76991
-        const turbopackWarningText = 'Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.\nTry to install it into the project directory by running';
-        // TODO 4.0: Remove this once we drop support for Next.js 15.2.x
-        const turbopackConfigWarningText = "Unrecognized key(s) in object: 'turbopack'";
-        const consoleWarn = console.warn;
-        console.warn = (...args)=>{
-            // Force to disable serverExternalPackages warnings: https://github.com/vercel/next.js/issues/68805
-            if (typeof args[1] === 'string' && args[1].includes(turbopackWarningText) || typeof args[0] === 'string' && args[0].includes(turbopackWarningText)) {
-                return;
-            }
-            // Add Payload-specific message after turbopack config warning in Next.js 15.2.x or lower.
-            // TODO 4.0: Remove this once we drop support for Next.js 15.2.x
-            const hasTurbopackConfigWarning = typeof args[1] === 'string' && args[1].includes(turbopackConfigWarningText) || typeof args[0] === 'string' && args[0].includes(turbopackConfigWarningText);
-            if (hasTurbopackConfigWarning) {
-                consoleWarn(...args);
-                consoleWarn('Payload: You can safely ignore the "Invalid next.config" warning above. This only occurs on Next.js 15.2.x or lower. We recommend upgrading to Next.js 15.4.7 to resolve this warning.');
-                return;
-            }
-            consoleWarn(...args);
-        };
-    }
-    const isBuild = process.env.NODE_ENV === 'production';
-    const isTurbopackNextjs15 = process.env.TURBOPACK === '1';
-    const isTurbopackNextjs16 = process.env.TURBOPACK === 'auto';
-    if (isBuild && (isTurbopackNextjs15 || isTurbopackNextjs16)) {
-        throw new Error('Payload does not support using Turbopack for production builds. If you are using Next.js 16, please use `next build --webpack` instead.');
-    }
-    const poweredByHeader = {
-        key: 'X-Powered-By',
-        value: 'Next.js, Payload'
-    };
+ * */
+export const withPayload = (nextConfig = {}, options = {}) => {
+  const nextjsVersion = getNextjsVersion();
+  const supportsTurbopackBuild = supportsTurbopackExternalizeTransitiveDependencies(nextjsVersion);
+  const env = nextConfig.env || {};
+  if (nextConfig.experimental?.staleTimes?.dynamic) {
+    console.warn('Payload detected a non-zero value for the `staleTimes.dynamic` option in your Next.js config. This will slow down page transitions and may cause stale data to load within the Admin panel. To clear this warning, remove the `staleTimes.dynamic` option from your Next.js config or set it to 0. In the future, Next.js may support scoping this option to specific routes.');
+    env.NEXT_PUBLIC_ENABLE_ROUTER_CACHE_REFRESH = 'true';
+  }
+  const baseConfig = {
+    ...nextConfig,
+    env,
+    outputFileTracingExcludes: {
+      ...(nextConfig.outputFileTracingExcludes || {}),
+      '**/*': [...(nextConfig.outputFileTracingExcludes?.['**/*'] || []), 'drizzle-kit', 'drizzle-kit/api']
+    },
+    outputFileTracingIncludes: {
+      ...(nextConfig.outputFileTracingIncludes || {}),
+      '**/*': [...(nextConfig.outputFileTracingIncludes?.['**/*'] || []), '@libsql/client']
+    },
+    turbopack: {
+      ...(nextConfig.turbopack || {})
+    },
+    // We disable the poweredByHeader here because we add it manually in the headers function below
+    ...(nextConfig.poweredByHeader !== false ? {
+      poweredByHeader: false
+    } : {}),
+    headers: async () => {
+      const headersFromConfig = 'headers' in nextConfig ? await nextConfig.headers() : [];
+      return [...(headersFromConfig || []), {
+        headers: [{
+          key: 'Accept-CH',
+          value: 'Sec-CH-Prefers-Color-Scheme'
+        }, {
+          key: 'Vary',
+          value: 'Sec-CH-Prefers-Color-Scheme'
+        }, {
+          key: 'Critical-CH',
+          value: 'Sec-CH-Prefers-Color-Scheme'
+        }, ...(nextConfig.poweredByHeader !== false ? [poweredByHeader] : [])],
+        source: '/:path*'
+      }];
+    },
+    serverExternalPackages: [
+    // WHY: without externalizing graphql, a graphql version error will be thrown
+    // during runtime ("Ensure that there is only one instance of \"graphql\" in the node_modules\ndirectory.")
+    'graphql', ...(process.env.NODE_ENV === 'development' && options.devBundleServerPackages !== true ?
     /**
-   * @type {import('next').NextConfig}
-   */ const toReturn = {
-        ...nextConfig,
-        env,
-        turbopack: {
-            ...nextConfig.turbopack || {}
-        },
-        outputFileTracingExcludes: {
-            ...nextConfig.outputFileTracingExcludes || {},
-            '**/*': [
-                ...nextConfig.outputFileTracingExcludes?.['**/*'] || [],
-                'drizzle-kit',
-                'drizzle-kit/api'
-            ]
-        },
-        outputFileTracingIncludes: {
-            ...nextConfig.outputFileTracingIncludes || {},
-            '**/*': [
-                ...nextConfig.outputFileTracingIncludes?.['**/*'] || [],
-                '@libsql/client'
-            ]
-        },
-        // We disable the poweredByHeader here because we add it manually in the headers function below
-        ...nextConfig.poweredByHeader !== false ? {
-            poweredByHeader: false
-        } : {},
-        headers: async ()=>{
-            const headersFromConfig = 'headers' in nextConfig ? await nextConfig.headers() : [];
-            return [
-                ...headersFromConfig || [],
-                {
-                    source: '/:path*',
-                    headers: [
-                        {
-                            key: 'Accept-CH',
-                            value: 'Sec-CH-Prefers-Color-Scheme'
-                        },
-                        {
-                            key: 'Vary',
-                            value: 'Sec-CH-Prefers-Color-Scheme'
-                        },
-                        {
-                            key: 'Critical-CH',
-                            value: 'Sec-CH-Prefers-Color-Scheme'
-                        },
-                        ...nextConfig.poweredByHeader !== false ? [
-                            poweredByHeader
-                        ] : []
-                    ]
-                }
-            ];
-        },
-        serverExternalPackages: [
-            // serverExternalPackages = webpack.externals, but with turbopack support and an additional check
-            // for whether the package is resolvable from the project root
-            ...nextConfig.serverExternalPackages || [],
-            // Can be externalized, because we require users to install graphql themselves - we only rely on it as a peer dependency => resolvable from the project root.
-            //
-            // WHY: without externalizing graphql, a graphql version error will be thrown
-            // during runtime ("Ensure that there is only one instance of \"graphql\" in the node_modules\ndirectory.")
-            'graphql',
-            // External, because it installs import-in-the-middle and require-in-the-middle - both in the default serverExternalPackages list.
-            '@sentry/nextjs',
-            ...process.env.NODE_ENV === 'development' && options.devBundleServerPackages !== true ? /**
-           * Unless explicitly disabled by the user, by passing `devBundleServerPackages: true` to withPayload, we
-           * do not bundle server-only packages during dev for two reasons:
-           *
-           * 1. Performance: Fewer files to compile means faster compilation speeds.
-           * 2. Turbopack support: Webpack's externals are not supported by Turbopack.
-           *
-           * Regarding Turbopack support: Unlike webpack.externals, we cannot use serverExternalPackages to
-           * externalized packages that are not resolvable from the project root. So including a package like
-           * "drizzle-kit" in here would do nothing - Next.js will ignore the rule and still bundle the package -
-           * because it detects that the package is not resolvable from the project root (= not directly installed
-           * by the user in their own package.json).
-           *
-           * Instead, we can use serverExternalPackages for the entry-point packages that *are* installed directly
-           * by the user (e.g. db-postgres, which then installs drizzle-kit as a dependency).
-           *
-           *
-           *
-           * We should only do this during development, not build, because externalizing these packages can hurt
-           * the bundle size. Not only does it disable tree-shaking, it also risks installing duplicate copies of the
-           * same package.
-           *
-           * Example:
-           * - @payloadcms/richtext-lexical (in bundle) -> installs qs-esm (bundled because of importer)
-           * - payload (not in bundle, external) -> installs qs-esm (external because of importer)
-           * Result: we have two copies of qs-esm installed - one in the bundle, and one in node_modules.
-           *
-           * During development, these bundle size difference do not matter much, and development speed /
-           * turbopack support are more important.
-           */ [
-                'payload',
-                '@payloadcms/db-mongodb',
-                '@payloadcms/db-postgres',
-                '@payloadcms/db-sqlite',
-                '@payloadcms/db-vercel-postgres',
-                '@payloadcms/db-d1-sqlite',
-                '@payloadcms/drizzle',
-                '@payloadcms/email-nodemailer',
-                '@payloadcms/email-resend',
-                '@payloadcms/graphql',
-                '@payloadcms/payload-cloud',
-                '@payloadcms/plugin-redirects'
-            ] : // TODO: Add the following packages, excluding their /client subpath exports, once Next.js supports it
-            // see: https://github.com/vercel/next.js/discussions/76991
-            //'@payloadcms/plugin-cloud-storage',
-            //'@payloadcms/plugin-sentry',
-            //'@payloadcms/plugin-stripe',
-            // @payloadcms/richtext-lexical
-            //'@payloadcms/storage-azure',
-            //'@payloadcms/storage-gcs',
-            //'@payloadcms/storage-s3',
-            //'@payloadcms/storage-uploadthing',
-            //'@payloadcms/storage-vercel-blob',
-            []
-        ],
-        webpack: (webpackConfig, webpackOptions)=>{
-            const incomingWebpackConfig = typeof nextConfig.webpack === 'function' ? nextConfig.webpack(webpackConfig, webpackOptions) : webpackConfig;
-            return {
-                ...incomingWebpackConfig,
-                externals: [
-                    ...incomingWebpackConfig?.externals || [],
-                    /**
-           * See the explanation in the serverExternalPackages section above.
-           * We need to force Webpack to emit require() calls for these packages, even though they are not
-           * resolvable from the project root. You would expect this to error during runtime, but Next.js seems to be able to require these just fine.
-           *
-           * This is the only way to get Webpack Build to work, without the bundle size caveats of externalizing the
-           * entry point packages, as explained in the serverExternalPackages section above.
-           */ 'drizzle-kit',
-                    'drizzle-kit/api',
-                    'sharp',
-                    'libsql',
-                    'require-in-the-middle'
-                ],
-                resolve: {
-                    ...incomingWebpackConfig?.resolve || {},
-                    alias: {
-                        ...incomingWebpackConfig?.resolve?.alias || {}
-                    },
-                    fallback: {
-                        ...incomingWebpackConfig?.resolve?.fallback || {},
-                        /*
-             * This fixes the following warning when running next build with webpack (tested on Next.js 16.0.3 with Payload 3.64.0):
-             *
-             * ⚠ Compiled with warnings in 8.7s
-             *
-             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/deps.js
-             * Module not found: Can't resolve 'aws4' in '/Users/alessio/Documents/temp/next16p/node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib'
-             *
-             * Import trace for requested module:
-             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/deps.js
-             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/client-side-encryption/client_encryption.js
-             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/index.js
-             * ./node_modules/.pnpm/mongoose@8.15.1/node_modules/mongoose/lib/index.js
-             * ./node_modules/.pnpm/mongoose@8.15.1/node_modules/mongoose/index.js
-             * ./node_modules/.pnpm/@payloadcms+db-mongodb@3.64.0_payload@3.64.0_graphql@16.12.0_typescript@5.7.3_/node_modules/@payloadcms/db-mongodb/dist/index.js
-             * ./src/payload.config.ts
-             * ./src/app/my-route/route.ts
-             *
-             **/ aws4: false
-                    }
-                },
-                plugins: [
-                    ...incomingWebpackConfig?.plugins || [],
-                    // Fix cloudflare:sockets error: https://github.com/vercel/next.js/discussions/50177
-                    new webpackOptions.webpack.IgnorePlugin({
-                        resourceRegExp: /^pg-native$|^cloudflare:sockets$/
-                    })
-                ]
-            };
+    * Unless explicitly disabled by the user, by passing `devBundleServerPackages: true` to withPayload, we
+    * do not bundle server-only packages during dev for two reasons:
+    *
+    * 1. Performance: Fewer files to compile means faster compilation speeds.
+    * 2. Turbopack support: Webpack's externals are not supported by Turbopack.
+    *
+    * Regarding Turbopack support: Unlike webpack.externals, we cannot use serverExternalPackages to
+    * externalized packages that are not resolvable from the project root. So including a package like
+    * "drizzle-kit" in here would do nothing - Next.js will ignore the rule and still bundle the package -
+    * because it detects that the package is not resolvable from the project root (= not directly installed
+    * by the user in their own package.json).
+    *
+    * Instead, we can use serverExternalPackages for the entry-point packages that *are* installed directly
+    * by the user (e.g. db-postgres, which then installs drizzle-kit as a dependency).
+    *
+    *
+    *
+    * We should only do this during development, not build, because externalizing these packages can hurt
+    * the bundle size. Not only does it disable tree-shaking, it also risks installing duplicate copies of the
+    * same package.
+    *
+    * Example:
+    * - @payloadcms/richtext-lexical (in bundle) -> installs qs-esm (bundled because of importer)
+    * - payload (not in bundle, external) -> installs qs-esm (external because of importer)
+    * Result: we have two copies of qs-esm installed - one in the bundle, and one in node_modules.
+    *
+    * During development, these bundle size difference do not matter much, and development speed /
+    * turbopack support are more important.
+    */
+    ['payload', '@payloadcms/db-mongodb', '@payloadcms/db-postgres', '@payloadcms/db-sqlite', '@payloadcms/db-vercel-postgres', '@payloadcms/db-d1-sqlite', '@payloadcms/drizzle', '@payloadcms/email-nodemailer', '@payloadcms/email-resend', '@payloadcms/graphql', '@payloadcms/payload-cloud', '@payloadcms/plugin-redirects'] : [])],
+    webpack: (webpackConfig, webpackOptions) => {
+      const incomingWebpackConfig = typeof nextConfig.webpack === 'function' ? nextConfig.webpack(webpackConfig, webpackOptions) : webpackConfig;
+      return {
+        ...incomingWebpackConfig,
+        externals: [...(incomingWebpackConfig?.externals || []),
+        /**
+        * See the explanation in the serverExternalPackages section above.
+        * We need to force Webpack to emit require() calls for these packages, even though they are not
+        * resolvable from the project root. You would expect this to error during runtime, but Next.js seems to be able to require these just fine.
+        *
+        * This is the only way to get Webpack Build to work, without the bundle size caveats of externalizing the
+        * entry point packages, as explained in the serverExternalPackages section above.
+        */
+        'drizzle-kit', 'drizzle-kit/api', 'sharp', 'libsql', 'require-in-the-middle'],
+        plugins: [...(incomingWebpackConfig?.plugins || []),
+        // Fix cloudflare:sockets error: https://github.com/vercel/next.js/discussions/50177
+        new webpackOptions.webpack.IgnorePlugin({
+          resourceRegExp: /^pg-native$|^cloudflare:sockets$/
+        })],
+        resolve: {
+          ...(incomingWebpackConfig?.resolve || {}),
+          alias: {
+            ...(incomingWebpackConfig?.resolve?.alias || {})
+          },
+          fallback: {
+            ...(incomingWebpackConfig?.resolve?.fallback || {}),
+            /*
+            * This fixes the following warning when running next build with webpack (tested on Next.js 16.0.3 with Payload 3.64.0):
+            *
+            * ⚠ Compiled with warnings in 8.7s
+            *
+            * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/deps.js
+            * Module not found: Can't resolve 'aws4' in '/Users/alessio/Documents/temp/next16p/node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib'
+            *
+            * Import trace for requested module:
+            * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/deps.js
+            * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/client-side-encryption/client_encryption.js
+            * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/index.js
+            * ./node_modules/.pnpm/mongoose@8.15.1/node_modules/mongoose/lib/index.js
+            * ./node_modules/.pnpm/mongoose@8.15.1/node_modules/mongoose/index.js
+            * ./node_modules/.pnpm/@payloadcms+db-mongodb@3.64.0_payload@3.64.0_graphql@16.12.0_typescript@5.7.3_/node_modules/@payloadcms/db-mongodb/dist/index.js
+            * ./src/payload.config.ts
+            * ./src/app/my-route/route.ts
+            *
+            **/
+            aws4: false
+          }
         }
-    };
-    if (nextConfig.basePath) {
-        toReturn.env.NEXT_BASE_PATH = nextConfig.basePath;
+      };
     }
-    return toReturn;
+  };
+  if (nextConfig.basePath) {
+    baseConfig.env.NEXT_BASE_PATH = nextConfig.basePath;
+  }
+  if (!supportsTurbopackBuild) {
+    return withPayloadLegacy(baseConfig);
+  } else {
+    return {
+      ...baseConfig,
+      serverExternalPackages: [...(baseConfig.serverExternalPackages || []), 'drizzle-kit', 'drizzle-kit/api', 'sharp', 'libsql', 'require-in-the-middle',
+      // Prevents turbopack build errors by the thread-stream package which is installed by pino
+      'pino']
+    };
+  }
 };
 export default withPayload;
-
 //# sourceMappingURL=withPayload.js.map

package/dist/withPayload.js.map

@@ -1 +1 @@
-{"version":3,"sources":["../src/withPayload.js"],"sourcesContent":["/**\n * @param {import('next').NextConfig} nextConfig\n * @param {Object} [options] - Optional configuration options\n * @param {boolean} [options.devBundleServerPackages] - Whether to bundle server packages in development mode. @default false\n *\n * @returns {import('next').NextConfig}\n * */\nexport const withPayload = (nextConfig = {}, options = {}) => {\n  const env = nextConfig.env || {}\n\n  if (nextConfig.experimental?.staleTimes?.dynamic) {\n    console.warn(\n      'Payload detected a non-zero value for the `staleTimes.dynamic` option in your Next.js config. This will slow down page transitions and may cause stale data to load within the Admin panel. To clear this warning, remove the `staleTimes.dynamic` option from your Next.js config or set it to 0. In the future, Next.js may support scoping this option to specific routes.',\n    )\n    env.NEXT_PUBLIC_ENABLE_ROUTER_CACHE_REFRESH = 'true'\n  }\n\n  if (process.env.PAYLOAD_PATCH_TURBOPACK_WARNINGS !== 'false') {\n    // TODO: This warning is thrown because we cannot externalize the entry-point package for client-s3, so we patch the warning to not show it.\n    // We can remove this once Next.js implements https://github.com/vercel/next.js/discussions/76991\n    const turbopackWarningText =\n      'Packages that should be external need to be installed in the project directory, so they can be resolved from the output files.\\nTry to install it into the project directory by running'\n\n    // TODO 4.0: Remove this once we drop support for Next.js 15.2.x\n    const turbopackConfigWarningText = \"Unrecognized key(s) in object: 'turbopack'\"\n\n    const consoleWarn = console.warn\n    console.warn = (...args) => {\n      // Force to disable serverExternalPackages warnings: https://github.com/vercel/next.js/issues/68805\n      if (\n        (typeof args[1] === 'string' && args[1].includes(turbopackWarningText)) ||\n        (typeof args[0] === 'string' && args[0].includes(turbopackWarningText))\n      ) {\n        return\n      }\n\n      // Add Payload-specific message after turbopack config warning in Next.js 15.2.x or lower.\n      // TODO 4.0: Remove this once we drop support for Next.js 15.2.x\n      const hasTurbopackConfigWarning =\n        (typeof args[1] === 'string' && args[1].includes(turbopackConfigWarningText)) ||\n        (typeof args[0] === 'string' && args[0].includes(turbopackConfigWarningText))\n\n      if (hasTurbopackConfigWarning) {\n        consoleWarn(...args)\n        consoleWarn(\n          'Payload: You can safely ignore the \"Invalid next.config\" warning above. This only occurs on Next.js 15.2.x or lower. We recommend upgrading to Next.js 15.4.7 to resolve this warning.',\n        )\n        return\n      }\n\n      consoleWarn(...args)\n    }\n  }\n\n  const isBuild = process.env.NODE_ENV === 'production'\n  const isTurbopackNextjs15 = process.env.TURBOPACK === '1'\n  const isTurbopackNextjs16 = process.env.TURBOPACK === 'auto'\n\n  if (isBuild && (isTurbopackNextjs15 || isTurbopackNextjs16)) {\n    throw new Error(\n      'Payload does not support using Turbopack for production builds. If you are using Next.js 16, please use `next build --webpack` instead.',\n    )\n  }\n\n  const poweredByHeader = {\n    key: 'X-Powered-By',\n    value: 'Next.js, Payload',\n  }\n\n  /**\n   * @type {import('next').NextConfig}\n   */\n  const toReturn = {\n    ...nextConfig,\n    env,\n    turbopack: {\n      ...(nextConfig.turbopack || {}),\n    },\n    outputFileTracingExcludes: {\n      ...(nextConfig.outputFileTracingExcludes || {}),\n      '**/*': [\n        ...(nextConfig.outputFileTracingExcludes?.['**/*'] || []),\n        'drizzle-kit',\n        'drizzle-kit/api',\n      ],\n    },\n    outputFileTracingIncludes: {\n      ...(nextConfig.outputFileTracingIncludes || {}),\n      '**/*': [...(nextConfig.outputFileTracingIncludes?.['**/*'] || []), '@libsql/client'],\n    },\n    // We disable the poweredByHeader here because we add it manually in the headers function below\n    ...(nextConfig.poweredByHeader !== false ? { poweredByHeader: false } : {}),\n    headers: async () => {\n      const headersFromConfig = 'headers' in nextConfig ? await nextConfig.headers() : []\n\n      return [\n        ...(headersFromConfig || []),\n        {\n          source: '/:path*',\n          headers: [\n            {\n              key: 'Accept-CH',\n              value: 'Sec-CH-Prefers-Color-Scheme',\n            },\n            {\n              key: 'Vary',\n              value: 'Sec-CH-Prefers-Color-Scheme',\n            },\n            {\n              key: 'Critical-CH',\n              value: 'Sec-CH-Prefers-Color-Scheme',\n            },\n            ...(nextConfig.poweredByHeader !== false ? [poweredByHeader] : []),\n          ],\n        },\n      ]\n    },\n    serverExternalPackages: [\n      // serverExternalPackages = webpack.externals, but with turbopack support and an additional check\n      // for whether the package is resolvable from the project root\n      ...(nextConfig.serverExternalPackages || []),\n      // Can be externalized, because we require users to install graphql themselves - we only rely on it as a peer dependency => resolvable from the project root.\n      //\n      // WHY: without externalizing graphql, a graphql version error will be thrown\n      // during runtime (\"Ensure that there is only one instance of \\\"graphql\\\" in the node_modules\\ndirectory.\")\n      'graphql',\n      // External, because it installs import-in-the-middle and require-in-the-middle - both in the default serverExternalPackages list.\n      '@sentry/nextjs',\n      ...(process.env.NODE_ENV === 'development' && options.devBundleServerPackages !== true\n        ? /**\n           * Unless explicitly disabled by the user, by passing `devBundleServerPackages: true` to withPayload, we\n           * do not bundle server-only packages during dev for two reasons:\n           *\n           * 1. Performance: Fewer files to compile means faster compilation speeds.\n           * 2. Turbopack support: Webpack's externals are not supported by Turbopack.\n           *\n           * Regarding Turbopack support: Unlike webpack.externals, we cannot use serverExternalPackages to\n           * externalized packages that are not resolvable from the project root. So including a package like\n           * \"drizzle-kit\" in here would do nothing - Next.js will ignore the rule and still bundle the package -\n           * because it detects that the package is not resolvable from the project root (= not directly installed\n           * by the user in their own package.json).\n           *\n           * Instead, we can use serverExternalPackages for the entry-point packages that *are* installed directly\n           * by the user (e.g. db-postgres, which then installs drizzle-kit as a dependency).\n           *\n           *\n           *\n           * We should only do this during development, not build, because externalizing these packages can hurt\n           * the bundle size. Not only does it disable tree-shaking, it also risks installing duplicate copies of the\n           * same package.\n           *\n           * Example:\n           * - @payloadcms/richtext-lexical (in bundle) -> installs qs-esm (bundled because of importer)\n           * - payload (not in bundle, external) -> installs qs-esm (external because of importer)\n           * Result: we have two copies of qs-esm installed - one in the bundle, and one in node_modules.\n           *\n           * During development, these bundle size difference do not matter much, and development speed /\n           * turbopack support are more important.\n           */\n          [\n            'payload',\n            '@payloadcms/db-mongodb',\n            '@payloadcms/db-postgres',\n            '@payloadcms/db-sqlite',\n            '@payloadcms/db-vercel-postgres',\n            '@payloadcms/db-d1-sqlite',\n            '@payloadcms/drizzle',\n            '@payloadcms/email-nodemailer',\n            '@payloadcms/email-resend',\n            '@payloadcms/graphql',\n            '@payloadcms/payload-cloud',\n            '@payloadcms/plugin-redirects',\n            // TODO: Add the following packages, excluding their /client subpath exports, once Next.js supports it\n            // see: https://github.com/vercel/next.js/discussions/76991\n            //'@payloadcms/plugin-cloud-storage',\n            //'@payloadcms/plugin-sentry',\n            //'@payloadcms/plugin-stripe',\n            // @payloadcms/richtext-lexical\n            //'@payloadcms/storage-azure',\n            //'@payloadcms/storage-gcs',\n            //'@payloadcms/storage-s3',\n            //'@payloadcms/storage-uploadthing',\n            //'@payloadcms/storage-vercel-blob',\n          ]\n        : []),\n    ],\n    webpack: (webpackConfig, webpackOptions) => {\n      const incomingWebpackConfig =\n        typeof nextConfig.webpack === 'function'\n          ? nextConfig.webpack(webpackConfig, webpackOptions)\n          : webpackConfig\n\n      return {\n        ...incomingWebpackConfig,\n        externals: [\n          ...(incomingWebpackConfig?.externals || []),\n          /**\n           * See the explanation in the serverExternalPackages section above.\n           * We need to force Webpack to emit require() calls for these packages, even though they are not\n           * resolvable from the project root. You would expect this to error during runtime, but Next.js seems to be able to require these just fine.\n           *\n           * This is the only way to get Webpack Build to work, without the bundle size caveats of externalizing the\n           * entry point packages, as explained in the serverExternalPackages section above.\n           */\n          'drizzle-kit',\n          'drizzle-kit/api',\n          'sharp',\n          'libsql',\n          'require-in-the-middle',\n        ],\n        resolve: {\n          ...(incomingWebpackConfig?.resolve || {}),\n          alias: {\n            ...(incomingWebpackConfig?.resolve?.alias || {}),\n          },\n          fallback: {\n            ...(incomingWebpackConfig?.resolve?.fallback || {}),\n            /*\n             * This fixes the following warning when running next build with webpack (tested on Next.js 16.0.3 with Payload 3.64.0):\n             *\n             * ⚠ Compiled with warnings in 8.7s\n             *\n             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/deps.js\n             * Module not found: Can't resolve 'aws4' in '/Users/alessio/Documents/temp/next16p/node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib'\n             *\n             * Import trace for requested module:\n             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/deps.js\n             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/client-side-encryption/client_encryption.js\n             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/index.js\n             * ./node_modules/.pnpm/mongoose@8.15.1/node_modules/mongoose/lib/index.js\n             * ./node_modules/.pnpm/mongoose@8.15.1/node_modules/mongoose/index.js\n             * ./node_modules/.pnpm/@payloadcms+db-mongodb@3.64.0_payload@3.64.0_graphql@16.12.0_typescript@5.7.3_/node_modules/@payloadcms/db-mongodb/dist/index.js\n             * ./src/payload.config.ts\n             * ./src/app/my-route/route.ts\n             *\n             **/\n            aws4: false,\n          },\n        },\n        plugins: [\n          ...(incomingWebpackConfig?.plugins || []),\n          // Fix cloudflare:sockets error: https://github.com/vercel/next.js/discussions/50177\n          new webpackOptions.webpack.IgnorePlugin({\n            resourceRegExp: /^pg-native$|^cloudflare:sockets$/,\n          }),\n        ],\n      }\n    },\n  }\n\n  if (nextConfig.basePath) {\n    toReturn.env.NEXT_BASE_PATH = nextConfig.basePath\n  }\n\n  return toReturn\n}\n\nexport default withPayload\n"],"names":["withPayload","nextConfig","options","env","experimental","staleTimes","dynamic","console","warn","NEXT_PUBLIC_ENABLE_ROUTER_CACHE_REFRESH","process","PAYLOAD_PATCH_TURBOPACK_WARNINGS","turbopackWarningText","turbopackConfigWarningText","consoleWarn","args","includes","hasTurbopackConfigWarning","isBuild","NODE_ENV","isTurbopackNextjs15","TURBOPACK","isTurbopackNextjs16","Error","poweredByHeader","key","value","toReturn","turbopack","outputFileTracingExcludes","outputFileTracingIncludes","headers","headersFromConfig","source","serverExternalPackages","devBundleServerPackages","webpack","webpackConfig","webpackOptions","incomingWebpackConfig","externals","resolve","alias","fallback","aws4","plugins","IgnorePlugin","resourceRegExp","basePath","NEXT_BASE_PATH"],"mappings":"AAAA;;;;;;GAMG,GACH,OAAO,MAAMA,cAAc,CAACC,aAAa,CAAC,CAAC,EAAEC,UAAU,CAAC,CAAC;IACvD,MAAMC,MAAMF,WAAWE,GAAG,IAAI,CAAC;IAE/B,IAAIF,WAAWG,YAAY,EAAEC,YAAYC,SAAS;QAChDC,QAAQC,IAAI,CACV;QAEFL,IAAIM,uCAAuC,GAAG;IAChD;IAEA,IAAIC,QAAQP,GAAG,CAACQ,gCAAgC,KAAK,SAAS;QAC5D,4IAA4I;QAC5I,iGAAiG;QACjG,MAAMC,uBACJ;QAEF,gEAAgE;QAChE,MAAMC,6BAA6B;QAEnC,MAAMC,cAAcP,QAAQC,IAAI;QAChCD,QAAQC,IAAI,GAAG,CAAC,GAAGO;YACjB,mGAAmG;YACnG,IACE,AAAC,OAAOA,IAAI,CAAC,EAAE,KAAK,YAAYA,IAAI,CAAC,EAAE,CAACC,QAAQ,CAACJ,yBAChD,OAAOG,IAAI,CAAC,EAAE,KAAK,YAAYA,IAAI,CAAC,EAAE,CAACC,QAAQ,CAACJ,uBACjD;gBACA;YACF;YAEA,0FAA0F;YAC1F,gEAAgE;YAChE,MAAMK,4BACJ,AAAC,OAAOF,IAAI,CAAC,EAAE,KAAK,YAAYA,IAAI,CAAC,EAAE,CAACC,QAAQ,CAACH,+BAChD,OAAOE,IAAI,CAAC,EAAE,KAAK,YAAYA,IAAI,CAAC,EAAE,CAACC,QAAQ,CAACH;YAEnD,IAAII,2BAA2B;gBAC7BH,eAAeC;gBACfD,YACE;gBAEF;YACF;YAEAA,eAAeC;QACjB;IACF;IAEA,MAAMG,UAAUR,QAAQP,GAAG,CAACgB,QAAQ,KAAK;IACzC,MAAMC,sBAAsBV,QAAQP,GAAG,CAACkB,SAAS,KAAK;IACtD,MAAMC,sBAAsBZ,QAAQP,GAAG,CAACkB,SAAS,KAAK;IAEtD,IAAIH,WAAYE,CAAAA,uBAAuBE,mBAAkB,GAAI;QAC3D,MAAM,IAAIC,MACR;IAEJ;IAEA,MAAMC,kBAAkB;QACtBC,KAAK;QACLC,OAAO;IACT;IAEA;;GAEC,GACD,MAAMC,WAAW;QACf,GAAG1B,UAAU;QACbE;QACAyB,WAAW;YACT,GAAI3B,WAAW2B,SAAS,IAAI,CAAC,CAAC;QAChC;QACAC,2BAA2B;YACzB,GAAI5B,WAAW4B,yBAAyB,IAAI,CAAC,CAAC;YAC9C,QAAQ;mBACF5B,WAAW4B,yBAAyB,EAAE,CAAC,OAAO,IAAI,EAAE;gBACxD;gBACA;aACD;QACH;QACAC,2BAA2B;YACzB,GAAI7B,WAAW6B,yBAAyB,IAAI,CAAC,CAAC;YAC9C,QAAQ;mBAAK7B,WAAW6B,yBAAyB,EAAE,CAAC,OAAO,IAAI,EAAE;gBAAG;aAAiB;QACvF;QACA,+FAA+F;QAC/F,GAAI7B,WAAWuB,eAAe,KAAK,QAAQ;YAAEA,iBAAiB;QAAM,IAAI,CAAC,CAAC;QAC1EO,SAAS;YACP,MAAMC,oBAAoB,aAAa/B,aAAa,MAAMA,WAAW8B,OAAO,KAAK,EAAE;YAEnF,OAAO;mBACDC,qBAAqB,EAAE;gBAC3B;oBACEC,QAAQ;oBACRF,SAAS;wBACP;4BACEN,KAAK;4BACLC,OAAO;wBACT;wBACA;4BACED,KAAK;4BACLC,OAAO;wBACT;wBACA;4BACED,KAAK;4BACLC,OAAO;wBACT;2BACIzB,WAAWuB,eAAe,KAAK,QAAQ;4BAACA;yBAAgB,GAAG,EAAE;qBAClE;gBACH;aACD;QACH;QACAU,wBAAwB;YACtB,iGAAiG;YACjG,8DAA8D;eAC1DjC,WAAWiC,sBAAsB,IAAI,EAAE;YAC3C,6JAA6J;YAC7J,EAAE;YACF,6EAA6E;YAC7E,2GAA2G;YAC3G;YACA,kIAAkI;YAClI;eACIxB,QAAQP,GAAG,CAACgB,QAAQ,KAAK,iBAAiBjB,QAAQiC,uBAAuB,KAAK,OAC9E;;;;;;;;;;;;;;;;;;;;;;;;;;;;;WA6BC,GACD;gBACE;gBACA;gBACA;gBACA;gBACA;gBACA;gBACA;gBACA;gBACA;gBACA;gBACA;gBACA;aAYD,GAXC,sGAAsG;YACtG,2DAA2D;YAC3D,qCAAqC;YACrC,8BAA8B;YAC9B,8BAA8B;YAC9B,+BAA+B;YAC/B,8BAA8B;YAC9B,4BAA4B;YAC5B,2BAA2B;YAC3B,oCAAoC;YACpC,oCAAoC;YAEtC,EAAE;SACP;QACDC,SAAS,CAACC,eAAeC;YACvB,MAAMC,wBACJ,OAAOtC,WAAWmC,OAAO,KAAK,aAC1BnC,WAAWmC,OAAO,CAACC,eAAeC,kBAClCD;YAEN,OAAO;gBACL,GAAGE,qBAAqB;gBACxBC,WAAW;uBACLD,uBAAuBC,aAAa,EAAE;oBAC1C;;;;;;;WAOC,GACD;oBACA;oBACA;oBACA;oBACA;iBACD;gBACDC,SAAS;oBACP,GAAIF,uBAAuBE,WAAW,CAAC,CAAC;oBACxCC,OAAO;wBACL,GAAIH,uBAAuBE,SAASC,SAAS,CAAC,CAAC;oBACjD;oBACAC,UAAU;wBACR,GAAIJ,uBAAuBE,SAASE,YAAY,CAAC,CAAC;wBAClD;;;;;;;;;;;;;;;;;;cAkBE,GACFC,MAAM;oBACR;gBACF;gBACAC,SAAS;uBACHN,uBAAuBM,WAAW,EAAE;oBACxC,oFAAoF;oBACpF,IAAIP,eAAeF,OAAO,CAACU,YAAY,CAAC;wBACtCC,gBAAgB;oBAClB;iBACD;YACH;QACF;IACF;IAEA,IAAI9C,WAAW+C,QAAQ,EAAE;QACvBrB,SAASxB,GAAG,CAAC8C,cAAc,GAAGhD,WAAW+C,QAAQ;IACnD;IAEA,OAAOrB;AACT,EAAC;AAED,eAAe3B,YAAW"}
+{"version":3,"file":"withPayload.js","names":["getNextjsVersion","supportsTurbopackExternalizeTransitiveDependencies","withPayloadLegacy","poweredByHeader","key","value","withPayload","nextConfig","options","nextjsVersion","supportsTurbopackBuild","env","experimental","staleTimes","dynamic","console","warn","NEXT_PUBLIC_ENABLE_ROUTER_CACHE_REFRESH","baseConfig","outputFileTracingExcludes","outputFileTracingIncludes","turbopack","headers","headersFromConfig","source","serverExternalPackages","process","NODE_ENV","devBundleServerPackages","webpack","webpackConfig","webpackOptions","incomingWebpackConfig","externals","plugins","IgnorePlugin","resourceRegExp","resolve","alias","fallback","aws4","basePath","NEXT_BASE_PATH"],"sources":["../src/withPayload.ts"],"sourcesContent":["/* eslint-disable no-console */\n/* eslint-disable no-restricted-exports */\nimport type { NextConfig } from 'next'\n\nimport {\n  getNextjsVersion,\n  supportsTurbopackExternalizeTransitiveDependencies,\n} from './withPayload.utils.js'\nimport { withPayloadLegacy } from './withPayloadLegacy.js'\n\nconst poweredByHeader = {\n  key: 'X-Powered-By',\n  value: 'Next.js, Payload',\n}\n\n/**\n * @param {import('next').NextConfig} nextConfig\n * @param {Object} [options] - Optional configuration options\n * @param {boolean} [options.devBundleServerPackages] - Whether to bundle server packages in development mode. @default false\n * */\nexport const withPayload = (\n  nextConfig: NextConfig = {},\n  options: { devBundleServerPackages?: boolean } = {},\n): NextConfig => {\n  const nextjsVersion = getNextjsVersion()\n\n  const supportsTurbopackBuild = supportsTurbopackExternalizeTransitiveDependencies(nextjsVersion)\n\n  const env = nextConfig.env || {}\n\n  if (nextConfig.experimental?.staleTimes?.dynamic) {\n    console.warn(\n      'Payload detected a non-zero value for the `staleTimes.dynamic` option in your Next.js config. This will slow down page transitions and may cause stale data to load within the Admin panel. To clear this warning, remove the `staleTimes.dynamic` option from your Next.js config or set it to 0. In the future, Next.js may support scoping this option to specific routes.',\n    )\n    env.NEXT_PUBLIC_ENABLE_ROUTER_CACHE_REFRESH = 'true'\n  }\n\n  const baseConfig: NextConfig = {\n    ...nextConfig,\n    env,\n    outputFileTracingExcludes: {\n      ...(nextConfig.outputFileTracingExcludes || {}),\n      '**/*': [\n        ...(nextConfig.outputFileTracingExcludes?.['**/*'] || []),\n        'drizzle-kit',\n        'drizzle-kit/api',\n      ],\n    },\n    outputFileTracingIncludes: {\n      ...(nextConfig.outputFileTracingIncludes || {}),\n      '**/*': [...(nextConfig.outputFileTracingIncludes?.['**/*'] || []), '@libsql/client'],\n    },\n    turbopack: {\n      ...(nextConfig.turbopack || {}),\n    },\n    // We disable the poweredByHeader here because we add it manually in the headers function below\n    ...(nextConfig.poweredByHeader !== false ? { poweredByHeader: false } : {}),\n    headers: async () => {\n      const headersFromConfig = 'headers' in nextConfig ? await nextConfig.headers() : []\n\n      return [\n        ...(headersFromConfig || []),\n        {\n          headers: [\n            {\n              key: 'Accept-CH',\n              value: 'Sec-CH-Prefers-Color-Scheme',\n            },\n            {\n              key: 'Vary',\n              value: 'Sec-CH-Prefers-Color-Scheme',\n            },\n            {\n              key: 'Critical-CH',\n              value: 'Sec-CH-Prefers-Color-Scheme',\n            },\n            ...(nextConfig.poweredByHeader !== false ? [poweredByHeader] : []),\n          ],\n          source: '/:path*',\n        },\n      ]\n    },\n    serverExternalPackages: [\n      // WHY: without externalizing graphql, a graphql version error will be thrown\n      // during runtime (\"Ensure that there is only one instance of \\\"graphql\\\" in the node_modules\\ndirectory.\")\n      'graphql',\n      ...(process.env.NODE_ENV === 'development' && options.devBundleServerPackages !== true\n        ? /**\n           * Unless explicitly disabled by the user, by passing `devBundleServerPackages: true` to withPayload, we\n           * do not bundle server-only packages during dev for two reasons:\n           *\n           * 1. Performance: Fewer files to compile means faster compilation speeds.\n           * 2. Turbopack support: Webpack's externals are not supported by Turbopack.\n           *\n           * Regarding Turbopack support: Unlike webpack.externals, we cannot use serverExternalPackages to\n           * externalized packages that are not resolvable from the project root. So including a package like\n           * \"drizzle-kit\" in here would do nothing - Next.js will ignore the rule and still bundle the package -\n           * because it detects that the package is not resolvable from the project root (= not directly installed\n           * by the user in their own package.json).\n           *\n           * Instead, we can use serverExternalPackages for the entry-point packages that *are* installed directly\n           * by the user (e.g. db-postgres, which then installs drizzle-kit as a dependency).\n           *\n           *\n           *\n           * We should only do this during development, not build, because externalizing these packages can hurt\n           * the bundle size. Not only does it disable tree-shaking, it also risks installing duplicate copies of the\n           * same package.\n           *\n           * Example:\n           * - @payloadcms/richtext-lexical (in bundle) -> installs qs-esm (bundled because of importer)\n           * - payload (not in bundle, external) -> installs qs-esm (external because of importer)\n           * Result: we have two copies of qs-esm installed - one in the bundle, and one in node_modules.\n           *\n           * During development, these bundle size difference do not matter much, and development speed /\n           * turbopack support are more important.\n           */\n          [\n            'payload',\n            '@payloadcms/db-mongodb',\n            '@payloadcms/db-postgres',\n            '@payloadcms/db-sqlite',\n            '@payloadcms/db-vercel-postgres',\n            '@payloadcms/db-d1-sqlite',\n            '@payloadcms/drizzle',\n            '@payloadcms/email-nodemailer',\n            '@payloadcms/email-resend',\n            '@payloadcms/graphql',\n            '@payloadcms/payload-cloud',\n            '@payloadcms/plugin-redirects',\n            // TODO: Add the following packages, excluding their /client subpath exports, once Next.js supports it\n            // see: https://github.com/vercel/next.js/discussions/76991\n            //'@payloadcms/plugin-cloud-storage',\n            //'@payloadcms/plugin-sentry',\n            //'@payloadcms/plugin-stripe',\n            // @payloadcms/richtext-lexical\n            //'@payloadcms/storage-azure',\n            //'@payloadcms/storage-gcs',\n            //'@payloadcms/storage-s3',\n            //'@payloadcms/storage-uploadthing',\n            //'@payloadcms/storage-vercel-blob',\n          ]\n        : []),\n    ],\n    webpack: (webpackConfig, webpackOptions) => {\n      const incomingWebpackConfig =\n        typeof nextConfig.webpack === 'function'\n          ? nextConfig.webpack(webpackConfig, webpackOptions)\n          : webpackConfig\n\n      return {\n        ...incomingWebpackConfig,\n        externals: [\n          ...(incomingWebpackConfig?.externals || []),\n          /**\n           * See the explanation in the serverExternalPackages section above.\n           * We need to force Webpack to emit require() calls for these packages, even though they are not\n           * resolvable from the project root. You would expect this to error during runtime, but Next.js seems to be able to require these just fine.\n           *\n           * This is the only way to get Webpack Build to work, without the bundle size caveats of externalizing the\n           * entry point packages, as explained in the serverExternalPackages section above.\n           */\n          'drizzle-kit',\n          'drizzle-kit/api',\n          'sharp',\n          'libsql',\n          'require-in-the-middle',\n        ],\n        plugins: [\n          ...(incomingWebpackConfig?.plugins || []),\n          // Fix cloudflare:sockets error: https://github.com/vercel/next.js/discussions/50177\n          new webpackOptions.webpack.IgnorePlugin({\n            resourceRegExp: /^pg-native$|^cloudflare:sockets$/,\n          }),\n        ],\n        resolve: {\n          ...(incomingWebpackConfig?.resolve || {}),\n          alias: {\n            ...(incomingWebpackConfig?.resolve?.alias || {}),\n          },\n          fallback: {\n            ...(incomingWebpackConfig?.resolve?.fallback || {}),\n            /*\n             * This fixes the following warning when running next build with webpack (tested on Next.js 16.0.3 with Payload 3.64.0):\n             *\n             * ⚠ Compiled with warnings in 8.7s\n             *\n             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/deps.js\n             * Module not found: Can't resolve 'aws4' in '/Users/alessio/Documents/temp/next16p/node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib'\n             *\n             * Import trace for requested module:\n             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/deps.js\n             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/client-side-encryption/client_encryption.js\n             * ./node_modules/.pnpm/mongodb@6.16.0/node_modules/mongodb/lib/index.js\n             * ./node_modules/.pnpm/mongoose@8.15.1/node_modules/mongoose/lib/index.js\n             * ./node_modules/.pnpm/mongoose@8.15.1/node_modules/mongoose/index.js\n             * ./node_modules/.pnpm/@payloadcms+db-mongodb@3.64.0_payload@3.64.0_graphql@16.12.0_typescript@5.7.3_/node_modules/@payloadcms/db-mongodb/dist/index.js\n             * ./src/payload.config.ts\n             * ./src/app/my-route/route.ts\n             *\n             **/\n            aws4: false,\n          },\n        },\n      }\n    },\n  }\n\n  if (nextConfig.basePath) {\n    baseConfig.env.NEXT_BASE_PATH = nextConfig.basePath\n  }\n\n  if (!supportsTurbopackBuild) {\n    return withPayloadLegacy(baseConfig)\n  } else {\n    return {\n      ...baseConfig,\n      serverExternalPackages: [\n        ...(baseConfig.serverExternalPackages || []),\n        'drizzle-kit',\n        'drizzle-kit/api',\n        'sharp',\n        'libsql',\n        'require-in-the-middle',\n        // Prevents turbopack build errors by the thread-stream package which is installed by pino\n        'pino',\n      ],\n    }\n  }\n}\n\nexport default withPayload\n"],"mappings":"AAAA,gCACA,0CAGA,SACEA,gBAAgB,EAChBC,kDAAkD,QAC7C;AACP,SAASC,iBAAiB,QAAQ;AAElC,MAAMC,eAAA,GAAkB;EACtBC,GAAA,EAAK;EACLC,KAAA,EAAO;AACT;AAEA;;;;;AAKA,OAAO,MAAMC,WAAA,GAAcA,CACzBC,UAAA,GAAyB,CAAC,CAAC,EAC3BC,OAAA,GAAiD,CAAC,CAAC;EAEnD,MAAMC,aAAA,GAAgBT,gBAAA;EAEtB,MAAMU,sBAAA,GAAyBT,kDAAA,CAAmDQ,aAAA;EAElF,MAAME,GAAA,GAAMJ,UAAA,CAAWI,GAAG,IAAI,CAAC;EAE/B,IAAIJ,UAAA,CAAWK,YAAY,EAAEC,UAAA,EAAYC,OAAA,EAAS;IAChDC,OAAA,CAAQC,IAAI,CACV;IAEFL,GAAA,CAAIM,uCAAuC,GAAG;EAChD;EAEA,MAAMC,UAAA,GAAyB;IAC7B,GAAGX,UAAU;IACbI,GAAA;IACAQ,yBAAA,EAA2B;MACzB,IAAIZ,UAAA,CAAWY,yBAAyB,IAAI,CAAC,CAAC;MAC9C,QAAQ,C,IACFZ,UAAA,CAAWY,yBAAyB,GAAG,OAAO,IAAI,EAAE,GACxD,eACA;IAEJ;IACAC,yBAAA,EAA2B;MACzB,IAAIb,UAAA,CAAWa,yBAAyB,IAAI,CAAC,CAAC;MAC9C,QAAQ,C,IAAKb,UAAA,CAAWa,yBAAyB,GAAG,OAAO,IAAI,EAAE,GAAG;IACtE;IACAC,SAAA,EAAW;MACT,IAAId,UAAA,CAAWc,SAAS,IAAI,CAAC,CAAC;IAChC;IACA;IACA,IAAId,UAAA,CAAWJ,eAAe,KAAK,QAAQ;MAAEA,eAAA,EAAiB;IAAM,IAAI,CAAC,CAAC;IAC1EmB,OAAA,EAAS,MAAAA,CAAA;MACP,MAAMC,iBAAA,GAAoB,aAAahB,UAAA,GAAa,MAAMA,UAAA,CAAWe,OAAO,KAAK,EAAE;MAEnF,OAAO,C,IACDC,iBAAA,IAAqB,EAAE,GAC3B;QACED,OAAA,EAAS,CACP;UACElB,GAAA,EAAK;UACLC,KAAA,EAAO;QACT,GACA;UACED,GAAA,EAAK;UACLC,KAAA,EAAO;QACT,GACA;UACED,GAAA,EAAK;UACLC,KAAA,EAAO;QACT,G,IACIE,UAAA,CAAWJ,eAAe,KAAK,QAAQ,CAACA,eAAA,CAAgB,GAAG,EAAE,EAClE;QACDqB,MAAA,EAAQ;MACV,EACD;IACH;IACAC,sBAAA,EAAwB;IACtB;IACA;IACA,W,IACIC,OAAA,CAAQf,GAAG,CAACgB,QAAQ,KAAK,iBAAiBnB,OAAA,CAAQoB,uBAAuB,KAAK;IAC9E;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;IA8BA,CACE,WACA,0BACA,2BACA,yBACA,kCACA,4BACA,uBACA,gCACA,4BACA,uBACA,6BACA,+BAYD,GACD,EAAE,EACP;IACDC,OAAA,EAASA,CAACC,aAAA,EAAeC,cAAA;MACvB,MAAMC,qBAAA,GACJ,OAAOzB,UAAA,CAAWsB,OAAO,KAAK,aAC1BtB,UAAA,CAAWsB,OAAO,CAACC,aAAA,EAAeC,cAAA,IAClCD,aAAA;MAEN,OAAO;QACL,GAAGE,qBAAqB;QACxBC,SAAA,EAAW,C,IACLD,qBAAA,EAAuBC,SAAA,IAAa,EAAE;QAC1C;;;;;;;;QAQA,eACA,mBACA,SACA,UACA,wBACD;QACDC,OAAA,EAAS,C,IACHF,qBAAA,EAAuBE,OAAA,IAAW,EAAE;QACxC;QACA,IAAIH,cAAA,CAAeF,OAAO,CAACM,YAAY,CAAC;UACtCC,cAAA,EAAgB;QAClB,GACD;QACDC,OAAA,EAAS;UACP,IAAIL,qBAAA,EAAuBK,OAAA,IAAW,CAAC,CAAC;UACxCC,KAAA,EAAO;YACL,IAAIN,qBAAA,EAAuBK,OAAA,EAASC,KAAA,IAAS,CAAC,CAAC;UACjD;UACAC,QAAA,EAAU;YACR,IAAIP,qBAAA,EAAuBK,OAAA,EAASE,QAAA,IAAY,CAAC,CAAC;YAClD;;;;;;;;;;;;;;;;;;;YAmBAC,IAAA,EAAM;UACR;QACF;MACF;IACF;EACF;EAEA,IAAIjC,UAAA,CAAWkC,QAAQ,EAAE;IACvBvB,UAAA,CAAWP,GAAG,CAAC+B,cAAc,GAAGnC,UAAA,CAAWkC,QAAQ;EACrD;EAEA,IAAI,CAAC/B,sBAAA,EAAwB;IAC3B,OAAOR,iBAAA,CAAkBgB,UAAA;EAC3B,OAAO;IACL,OAAO;MACL,GAAGA,UAAU;MACbO,sBAAA,EAAwB,C,IAClBP,UAAA,CAAWO,sBAAsB,IAAI,EAAE,GAC3C,eACA,mBACA,SACA,UACA;MACA;MACA;IAEJ;EACF;AACF;AAEA,eAAenB,WAAA","ignoreList":[]}

package/dist/withPayload.utils.d.ts

@@ -0,0 +1,58 @@
+/**
+ * This was taken and modified from https://github.com/getsentry/sentry-javascript/blob/15256034ee8150a5b7dcb97d23eca1a5486f0cae/packages/nextjs/src/config/util.ts
+ *
+ * MIT License
+ *
+ * Copyright (c) 2012 Functional Software, Inc. dba Sentry
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining a copy of
+ * this software and associated documentation files (the "Software"), to deal in
+ * the Software without restriction, including without limitation the rights to
+ * use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+ * of the Software, and to permit persons to whom the Software is furnished to do
+ * so, subject to the following conditions:
+ *
+ * The above copyright notice and this permission notice shall be included in all
+ * copies or substantial portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+ * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+ * SOFTWARE.
+ */
+/**
+ * Represents Semantic Versioning object
+ */
+type SemVer = {
+    buildmetadata?: string;
+    /**
+     * undefined if not a canary version
+     */
+    canaryVersion?: number;
+    major?: number;
+    minor?: number;
+    patch?: number;
+    prerelease?: string;
+};
+/**
+ * Parses input into a SemVer interface
+ * @param input string representation of a semver version
+ */
+export declare function parseSemver(input: string): SemVer;
+/**
+ * Returns the version of Next.js installed in the project, or undefined if it cannot be determined.
+ */
+export declare function getNextjsVersion(): SemVer | undefined;
+/**
+ * Checks if the current Next.js version supports native debug ids for turbopack.
+ * This feature was first introduced in Next.js v15.6.0-canary.36 and marked stable in Next.js v16
+ *
+ * @param version - version string to check.
+ * @returns true if Next.js version supports native debug ids for turbopack builds
+ */
+export declare function supportsTurbopackExternalizeTransitiveDependencies(version: SemVer | undefined): boolean;
+export {};
+//# sourceMappingURL=withPayload.utils.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"withPayload.utils.d.ts","sourceRoot":"","sources":["../src/withPayload.utils.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;;;;;;GAwBG;AAQH;;GAEG;AACH,KAAK,MAAM,GAAG;IACZ,aAAa,CAAC,EAAE,MAAM,CAAA;IACtB;;OAEG;IACH,aAAa,CAAC,EAAE,MAAM,CAAA;IACtB,KAAK,CAAC,EAAE,MAAM,CAAA;IACd,KAAK,CAAC,EAAE,MAAM,CAAA;IACd,KAAK,CAAC,EAAE,MAAM,CAAA;IACd,UAAU,CAAC,EAAE,MAAM,CAAA;CACpB,CAAA;AAMD;;;GAGG;AACH,wBAAgB,WAAW,CAAC,KAAK,EAAE,MAAM,GAAG,MAAM,CAmBjD;AAED;;GAEG;AACH,wBAAgB,gBAAgB,IAAI,MAAM,GAAG,SAAS,CAQrD;AAED;;;;;;GAMG;AACH,wBAAgB,kDAAkD,CAChE,OAAO,EAAE,MAAM,GAAG,SAAS,GAC1B,OAAO,CA+BT"}

package/dist/withPayload.utils.js

@@ -0,0 +1,101 @@
+/**
+ * This was taken and modified from https://github.com/getsentry/sentry-javascript/blob/15256034ee8150a5b7dcb97d23eca1a5486f0cae/packages/nextjs/src/config/util.ts
+ *
+ * MIT License
+ *
+ * Copyright (c) 2012 Functional Software, Inc. dba Sentry
+ *
+ * Permission is hereby granted, free of charge, to any person obtaining a copy of
+ * this software and associated documentation files (the "Software"), to deal in
+ * the Software without restriction, including without limitation the rights to
+ * use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+ * of the Software, and to permit persons to whom the Software is furnished to do
+ * so, subject to the following conditions:
+ *
+ * The above copyright notice and this permission notice shall be included in all
+ * copies or substantial portions of the Software.
+ *
+ * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+ * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+ * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+ * AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+ * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+ * OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+ * SOFTWARE.
+ */import { readFileSync } from 'fs';
+function _parseInt(input) {
+  return parseInt(input || '', 10);
+}
+// https://semver.org/#is-there-a-suggested-regular-expression-regex-to-check-a-semver-string
+const SEMVER_REGEXP = /^(0|[1-9]\d*)\.(0|[1-9]\d*)\.(0|[1-9]\d*)(?:-((?:0|[1-9]\d*|\d*[a-z-][0-9a-z-]*)(?:\.(?:0|[1-9]\d*|\d*[a-z-][0-9a-z-]*))*))?(?:\+([0-9a-z-]+(?:\.[0-9a-z-]+)*))?$/i;
+/**
+ * Parses input into a SemVer interface
+ * @param input string representation of a semver version
+ */
+export function parseSemver(input) {
+  const match = input.match(SEMVER_REGEXP) || [];
+  const major = _parseInt(match[1]);
+  const minor = _parseInt(match[2]);
+  const patch = _parseInt(match[3]);
+  const prerelease = match[4];
+  const canaryVersion = prerelease?.startsWith('canary.') ? parseInt(prerelease.split('.')[1] || '0', 10) : undefined;
+  return {
+    buildmetadata: match[5],
+    canaryVersion,
+    major: isNaN(major) ? undefined : major,
+    minor: isNaN(minor) ? undefined : minor,
+    patch: isNaN(patch) ? undefined : patch,
+    prerelease: match[4]
+  };
+}
+/**
+ * Returns the version of Next.js installed in the project, or undefined if it cannot be determined.
+ */
+export function getNextjsVersion() {
+  try {
+    const pkgUrl = import.meta.resolve('next/package.json');
+    const pkgJson = JSON.parse(readFileSync(new URL(pkgUrl), 'utf8'));
+    return parseSemver(pkgJson.version);
+  } catch {
+    return undefined;
+  }
+}
+/**
+ * Checks if the current Next.js version supports native debug ids for turbopack.
+ * This feature was first introduced in Next.js v15.6.0-canary.36 and marked stable in Next.js v16
+ *
+ * @param version - version string to check.
+ * @returns true if Next.js version supports native debug ids for turbopack builds
+ */
+export function supportsTurbopackExternalizeTransitiveDependencies(version) {
+  if (!version) {
+    return false;
+  }
+  const {
+    canaryVersion,
+    major,
+    minor
+  } = version;
+  if (major === undefined || minor === undefined) {
+    return false;
+  }
+  if (major > 16) {
+    return true;
+  }
+  if (major === 16) {
+    if (minor > 1) {
+      return true;
+    }
+    if (minor === 1) {
+      if (canaryVersion !== undefined) {
+        // 16.1.0-canary.15+
+        return canaryVersion >= 15;
+      } else {
+        // Assume that Next.js 16.1 inherits support for this feature from the canary release
+        return true;
+      }
+    }
+  }
+  return false;
+}
+//# sourceMappingURL=withPayload.utils.js.map