chore(deps): update dependency @opennextjs/cloudflare to v0.4.8

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@opennextjs/cloudflare (source)	0.4.0 -> 0.4.8

---

Release Notes

opennextjs/opennextjs-cloudflare (@​opennextjs/cloudflare)

v0.4.8

Compare Source

Patch Changes

• ac8b271: fix waitUntil

  Calling waitUntil/after was failing when mulitple requests were handled concurrently.
  This is fixed by pulling opennextjs/opennextjs-aws#733

• 761a312: import randomUUID from node:crypto to support NodeJS 18

v0.4.7

Compare Source

Patch Changes

• 420b598: Fix asset cache path

• a19b34d: perf: reduce CPU and memory usage by limiting code to AST parsing

• f30a5fe: bump @opennextjs/aws dependency to https://pkg.pr.new/@​opennextjs/aws@727

• 6791cea: Use kebab-case for the KV Cache.

• a630aea: fix: enable using the direct queue for isr

  The direct mode is not recommended for use in production as it does not de-dupe requests.

• f30a5fe: Fix: make sure that the kvCache doesn't serve stale cache values from assets when there is no KV binding

v0.4.6

Compare Source

Patch Changes

• 9561277: fix: remove dynamic require for map file

  ESBuild tries to load all files in the chunks folder with require("./chunks/" + var).
  This is an error when the folder contains map file.

v0.4.5

Compare Source

Patch Changes

• 1ccff65: bump @opennextjs/aws dependency to https://pkg.pr.new/@​opennextjs/aws@724

  this bump fixes rewrites to external urls not working when the external urls
  point to resources hosted on the Cloudflare network

• 30374b9: fix: Drop the module condition from ESBuild

  Because Next (via nft) does not use the module condition, ESBuild should not use it.
  Otherwise we might end up with missing files and a broken build.

v0.4.4

Compare Source

Patch Changes

• 6103547: fix: provide a proper error message when using getCloudflareContext in static routes

  getCloudflareContext can't be used in static routes, currently a misleading error
  message incorrectly tells the developer that they haven't called initOpenNextCloudflareForDev
  in their config file, this change updates such error message to properly clarify what
  the issue is (and how to solve it)

• 0a6191d: fix the encoding of __NEXT_PRIVATE_STANDALONE_CONFIG

• da7f8d8: fix: enable PPR with wrangler dev

• 714172d: fix: trailing slash redirect

• 0892679: fix: inline optional dependencies when bundling the server

v0.4.3

Compare Source

Patch Changes

• 9d45ee8: fix the error message of getCloudflareContext

  Hardcode function names that would get mangled otherwise.

• ac52954: bump the wrangler peer dependency (so to avoid multiple Using vars defined in .dev.vars logs during local development)

v0.4.2

Compare Source

Patch Changes

• 1b3a972: Dump ESBuild metadata to handler.mjs.meta.json

  The ESBuild metadata are written to a file alongside handler.mjs
  in .open-next/server-functions/default/...

• 5c90521: refactor: Make the list of optional dependencies configurable

• 67acb2f: fix build issues with @opentelemetry

  By using the pre-compiled library provided by Next.

• 3ed6cd1: fix: syntax error

v0.4.1

Compare Source

Patch Changes

• 1a2b815: fix: make sure that the initOpenNextCloudflareForDev() logic runs only 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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.