Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: make sure that the initOpenNextCloudflareForDev() logic runs only once #293

Merged

Conversation

dario-piotrowicz
Copy link
Contributor

@dario-piotrowicz dario-piotrowicz commented Jan 28, 2025

Currently calling initOpenNextCloudflareForDev() in the Next.js config file causes this initialization logic to run twice, consuming more resources and causing extra noise in the terminal logs, this change makes sure that the initialization logic is run only once instead

fixes half of #288

…nly once

Currently calling `initOpenNextCloudflareForDev()` in the Next.js config file causes
this initialization logic to run twice, consuming more resources and causing extra
noise in the terminal logs, this change makes sure that the initialization logic
is run only once instead
Copy link

changeset-bot bot commented Jan 28, 2025

🦋 Changeset detected

Latest commit: f0c4f9a

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

Copy link

pkg-pr-new bot commented Jan 28, 2025

Open in Stackblitz

pnpm add https://pkg.pr.new/@opennextjs/cloudflare@293

commit: f0c4f9a

@dario-piotrowicz dario-piotrowicz merged commit 1a2b815 into main Jan 28, 2025
7 checks passed
@dario-piotrowicz dario-piotrowicz deleted the dario/288/double-initOpenNextCloudflareForDev branch January 28, 2025 21:11
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.

2 participants