fix(platform): defer Node-only config behind async thunks

Webpack bundles the top level of each platform's next.platform.config.mjs
into the server output (because apps/site/mdx/plugins.mjs reads .mdx
from it), which meant the Cloudflare build shipped
`createRequire(...).resolve(...)` and `await getDeploymentId()` into the
worker runtime — failing at request time with `m.resolve is not a
function`. Moving the heavy, build-only pieces (`@opennextjs/cloudflare`
imports, `require.resolve`, VERCEL_URL computation) behind async thunks
keeps the module's top level free of Node-runtime-only code. Pair with
the webpack `conditionNames` wiring so `#platform/*` actually resolves
to the target variant at bundle time.

Author: ovflowd

apps/cloudflare/next.platform.config.mjs

@@ -1,49 +1,53 @@
-import { createRequire } from 'node:module';
-import { relative } from 'node:path';
-
-import { getDeploymentId } from '@opennextjs/cloudflare';
-
-const require = createRequire(import.meta.url);
-
 /**
  * Platform config contributed by the Cloudflare deployment target.
  *
- * Consumed by `apps/site/next.config.mjs` via the platform-config loader.
- * Must export a default `{ nextConfig, aliases, images }` shape — any of
- * which may be omitted when the platform has nothing to contribute.
+ * Consumed by `apps/site/next.config.mjs` via the `#platform/*` import
+ * map. Heavy, Node-only bits (`@opennextjs/cloudflare`, `createRequire`,
+ * `require.resolve`) live inside async thunks so that webpack — which
+ * bundles the top level of this module into the server output when
+ * `apps/site/mdx/plugins.mjs` reads `.mdx` — never drags them into the
+ * worker runtime.
  *
  * @type {import('../site/next.platform.config').PlatformConfig}
  */
 export default {
-  nextConfig: {
-    // Skew protection: Cloudflare routes requests by deploymentId so that
-    // a client and the worker stay in sync across rolling deploys.
-    deploymentId: await getDeploymentId(),
-  },
   aliases: {
     '@platform/analytics': '@node-core/platform-cloudflare/analytics',
     '@platform/instrumentation':
       '@node-core/platform-cloudflare/instrumentation',
   },
-  images: {
-    // Route optimized images through Cloudflare's Images service via the
-    // custom loader. `remotePatterns` do NOT apply here — Cloudflare
-    // enforces allowed origins at the edge instead.
-    loader: 'custom',
-    // Next.js joins `loaderFile` onto its own cwd (apps/site), so pass a
-    // path relative to that cwd rather than an absolute one. Resolving via
-    // `require.resolve` avoids the `new URL(..., import.meta.url)` pattern,
-    // which webpack rewrites as an asset reference and mangles at runtime.
-    loaderFile: relative(
-      process.cwd(),
-      require.resolve('@node-core/platform-cloudflare/image-loader')
-    ),
-  },
   mdx: {
     // Cloudflare workers can't load `shiki/wasm` via `WebAssembly.instantiate`
     // with custom imports (blocked for security), so fall back to the
     // JavaScript RegEx engine. Twoslash also needs a VFS we don't have here.
     wasm: false,
     twoslash: false,
   },
+  nextConfig: async () => {
+    const { getDeploymentId } = await import('@opennextjs/cloudflare');
+    return {
+      // Skew protection: Cloudflare routes requests by deploymentId so that
+      // a client and the worker stay in sync across rolling deploys.
+      deploymentId: await getDeploymentId(),
+    };
+  },
+  images: async () => {
+    const { createRequire } = await import('node:module');
+    const { relative } = await import('node:path');
+    const require = createRequire(import.meta.url);
+    return {
+      // Route optimized images through Cloudflare's Images service via the
+      // custom loader. `remotePatterns` do NOT apply here — Cloudflare
+      // enforces allowed origins at the edge instead.
+      loader: 'custom',
+      // Next.js joins `loaderFile` onto its own cwd (apps/site), so pass a
+      // path relative to that cwd rather than an absolute one. Resolving via
+      // `require.resolve` avoids the `new URL(..., import.meta.url)` pattern,
+      // which webpack rewrites as an asset reference and mangles at runtime.
+      loaderFile: relative(
+        process.cwd(),
+        require.resolve('@node-core/platform-cloudflare/image-loader')
+      ),
+    };
+  },
 };

apps/site/next.config.mjs

@@ -4,7 +4,11 @@ import createNextIntlPlugin from 'next-intl/plugin';
 
 import platform from '#platform/next.platform.config';
 
-import { BASE_PATH, ENABLE_STATIC_EXPORT } from './next.constants.mjs';
+import {
+  BASE_PATH,
+  ENABLE_STATIC_EXPORT,
+  DEPLOY_TARGET,
+} from './next.constants.mjs';
 import { getImagesConfig } from './next.image.config.mjs';
 import { redirects, rewrites } from './next.rewrites.mjs';
 
@@ -17,7 +21,7 @@ const nextConfig = {
   // We allow the BASE_PATH to be overridden in case that the Website
   // is being built on a subdirectory (e.g. /nodejs-website)
   basePath: BASE_PATH,
-  images: getImagesConfig(platform.images),
+  images: getImagesConfig(await platform.images?.()),
   serverExternalPackages: ['twoslash'],
   // Transpile platform packages' TSX/TS sources when they're pulled in via
   // the `@platform/*` aliases from the active `next.platform.config.mjs`.
@@ -78,12 +82,21 @@ const nextConfig = {
   },
   // Provide Turbopack Aliases for Platform Resolution
   turbopack: { resolveAlias: platform.aliases },
-  // Provide Webpack Aliases for Platform Resolution
+  // Provide Webpack Aliases for Platform Resolution. The active deployment
+  // target is also surfaced to the resolver via `conditionNames` so that
+  // `#platform/*` subpath imports in `package.json` pick the matching
+  // branch when webpack bundles server code.
   webpack: ({ resolve, ...config }) => ({
     ...config,
-    resolve: { ...resolve, alias: { ...resolve.alias, ...platform.aliases } },
+    resolve: {
+      ...resolve,
+      alias: { ...resolve.alias, ...platform.aliases },
+      conditionNames: resolve.conditionNames
+        .concat(DEPLOY_TARGET)
+        .filter(Boolean),
+    },
   }),
-  ...platform.nextConfig,
+  ...(await platform.nextConfig?.()),
 };
 
 const withNextIntl = createNextIntlPlugin('./i18n.tsx');

apps/site/next.platform.config.d.ts

@@ -7,12 +7,19 @@ type PlatformNextConfig = Pick<NextConfig, 'deploymentId' | 'env'>;
 /**
  * Shared platform-config contract consumed by `apps/site/next.config.mjs`
  * and implemented by each `@node-core/platform-<target>` package.
+ *
+ * `nextConfig` and `images` are async thunks so that platform modules
+ * that depend on Node-only tooling (e.g. `@opennextjs/cloudflare`,
+ * `require.resolve`) can keep those imports out of the module's
+ * top-level. Webpack bundles the top level of this module into the
+ * server output; deferring heavy work into function bodies keeps the
+ * worker runtime free of build-only code.
  */
 export type PlatformConfig = {
   aliases?: Record<string, string>;
-  images?: NextConfig['images'];
+  images?: () => Promise<NextConfig['images']>;
   mdx?: PlatformMdxConfig;
-  nextConfig?: PlatformNextConfig;
+  nextConfig?: () => Promise<PlatformNextConfig>;
 };
 
 declare const config: PlatformConfig;

apps/vercel/next.platform.config.mjs

@@ -1,26 +1,16 @@
 /**
  * Platform config contributed by the Vercel deployment target.
  *
- * Consumed by `apps/site/next.config.mjs` via the platform-config loader.
- * Must export a default `{ nextConfig, aliases, images }` shape — any of
- * which may be omitted when the platform has nothing to contribute.
+ * Consumed by `apps/site/next.config.mjs` via the `#platform/*` import
+ * map. Heavy, Node-only bits live inside async thunks so that webpack —
+ * which bundles the top level of this module into the server output
+ * when `apps/site/mdx/plugins.mjs` reads `.mdx` — never drags them into
+ * the Node server runtime (keeps bundles lean and parity with
+ * Cloudflare's contract).
  *
  * @type {import('../site/next.platform.config').PlatformConfig}
  */
-const VERCEL_URL = process.env.VERCEL_URL
-  ? `https://${process.env.VERCEL_URL}`
-  : undefined;
-
 export default {
-  nextConfig: {
-    // Expose Vercel's auto-assigned deployment URL as a platform-agnostic
-    // `NEXT_PUBLIC_BASE_URL` so `apps/site` consumers can read a single
-    // canonical env var. A manually-set `NEXT_PUBLIC_BASE_URL` wins.
-    env: {
-      NEXT_PUBLIC_BASE_URL:
-        process.env.NEXT_PUBLIC_BASE_URL || VERCEL_URL || '',
-    },
-  },
   aliases: {
     '@platform/analytics': '@node-core/platform-vercel/analytics',
     '@platform/instrumentation': '@node-core/platform-vercel/instrumentation',
@@ -31,4 +21,18 @@ export default {
     wasm: true,
     twoslash: true,
   },
+  nextConfig: async () => {
+    const VERCEL_URL = process.env.VERCEL_URL
+      ? `https://${process.env.VERCEL_URL}`
+      : undefined;
+    return {
+      // Expose Vercel's auto-assigned deployment URL as a platform-agnostic
+      // `NEXT_PUBLIC_BASE_URL` so `apps/site` consumers can read a single
+      // canonical env var. A manually-set `NEXT_PUBLIC_BASE_URL` wins.
+      env: {
+        NEXT_PUBLIC_BASE_URL:
+          process.env.NEXT_PUBLIC_BASE_URL || VERCEL_URL || '',
+      },
+    };
+  },
 };