update solution to use env filed instead

Author: dario-piotrowicz

packages/cloudflare/src/cli/commands/deploy.ts

@@ -56,7 +56,13 @@ export async function deployCommand(args: WithWranglerArgs<{ cacheChunkSize?: nu
 		],
 		{
 			logging: "all",
-			deploy: true,
+			env: {
+				// If we are running the deploy command we set this OPEN_NEXT_DEPLOY environment variable
+				// to let `wrangler deploy` know that it is being run from open-next. We do this because
+				// otherwise `wrangler deploy` run in an open-next project would call
+				// `opennextjs-cloudflare deploy` (thus causing an unwanted recursion).
+				OPEN_NEXT_DEPLOY: "true",
+			},
 		}
 	);
 }

packages/cloudflare/src/cli/utils/run-wrangler.ts

@@ -13,7 +13,7 @@ type WranglerOptions = {
 	environment?: string;
 	configPath?: string;
 	logging?: "all" | "error";
-	deploy?: boolean;
+	env?: Record<string, unknown>;
 };
 
 /**
@@ -84,11 +84,7 @@ export function runWrangler(options: BuildOptions, args: string[], wranglerOpts:
 				// Wrangler would load `.env.<wrangler env>` while we should load `.env.<process.env.NEXTJS_ENV>`
 				// See https://opennext.js.org/cloudflare/howtos/env-vars
 				CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV: "false",
-				// If we are running the deploy command we set this OPEN_NEXT_DEPLOY environment variable
-				// to let `wrangler deploy` know that it is being run from open-next. We do this because
-				// otherwise `wrangler deploy` run in an open-next project would call
-				// `opennextjs-cloudflare deploy` (thus causing an unwanted recursion).
-				...(wranglerOpts.deploy ? { OPEN_NEXT_DEPLOY: "true" } : {}),
+				...wranglerOpts.env,
 			},
 		}
 	);