Skip to content

Conversation

@dario-piotrowicz
Copy link
Contributor

@dario-piotrowicz dario-piotrowicz commented Dec 3, 2025

This is mostly beneficial just for wrangler deploy with autoconfig, since we're updating wrangler deploy to potentially call opennextjs-cloudflare deploy, the latter calls wrangler deploy so we need to have a mechanism in place for avoiding an infinite recursion in such cases

…ariable that wrangler can use to detect if it is run by open-next
@changeset-bot
Copy link

changeset-bot bot commented Dec 3, 2025

🦋 Changeset detected

Latest commit: 6db65ef

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@opennextjs/cloudflare Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@pkg-pr-new
Copy link

pkg-pr-new bot commented Dec 3, 2025

Open in StackBlitz

npm i https://pkg.pr.new/@opennextjs/cloudflare@1023

commit: 6db65ef

@dario-piotrowicz dario-piotrowicz requested a review from vicb December 4, 2025 13:07
}

export function runWrangler(options: BuildOptions, args: string[], wranglerOpts: WranglerOptions = {}) {
const isDeployCommand = args[0] === "deploy";
Copy link
Contributor

@vicb vicb Dec 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could you please reverse that and have the caller specify an (optional) extra env instead of trying to guess who called us here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants