chore(deps): update dependency @opennextjs/cloudflare to ^0.6.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@opennextjs/cloudflare (source)	^0.3.0 -> ^0.6.0

---

Release Notes

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

v0.6.5

Compare Source

Patch Changes

• #​514 3165593 Thanks @​vicb! - fix(middleware): enable wasm in bundled middleware

• #​515 cef5e03 Thanks @​vicb! - perf: optimize SQL queries

v0.6.4

Compare Source

Patch Changes

• #​512 96efdc1 Thanks @​james-elicx! - fix: yarn v4 not passing args to wrangler correctly

v0.6.3

Compare Source

Patch Changes

• #​509 42e2b5c Thanks @​ItsWendell! - fix: nextjs handler not detected in worker

v0.6.2

Compare Source

Patch Changes

• #​505 ce7516d Thanks @​james-elicx! - fix: npm failing to pass args to wrangler

v0.6.1

Compare Source

Patch Changes

• #​503 ba35663 Thanks @​james-elicx! - fix: bun failing to spawn wrangler

v0.6.0

Compare Source

Minor Changes

• #​499 5037f57 Thanks @​vicb! - Refactor the codebase for consistency

  BREAKING CHANGE

  Overrides:

  Overrides now live in @opennextjs/cloudflare/overrides and some files have been renamed.

  • Incremental cache overrides: @opennextjs/cloudflare/overrides/incremental-cache/...
  • Tag cache overrides: @opennextjs/cloudflare/overrides/tag-cache/...
  • Queue overrides: @opennextjs/cloudflare/overrides/queue/...

  For example the KV incremental cache override can be imported as @opennextjs/cloudflare/overrides/incremental-cache/kv-incremental-cache.

  Environment variables and bindings name changes:

  • NEXT_CACHE_WORKERS_KV -> NEXT_INC_CACHE_KV
  • NEXT_CACHE_R2_... -> NEXT_INC_CACHE_R2_...
  • NEXT_CACHE_D1 -> NEXT_TAG_CACHE_D1
  • NEXT_CACHE_DO_... -> NEXT_TAG_CACHE_DO_...
  • NEXT_CACHE_DO_REVALIDATION -> NEXT_CACHE_DO_QUEUE
  • NEXT_CACHE_REVALIDATION_WORKER -> WORKER_SELF_REFERENCE

  Other:

  NEXT_CACHE_D1_TAGS_TABLE and NEXT_CACHE_D1_REVALIDATIONS_TABLE have been dropped.
  The tables have a fixed names tags and revalidations.

• #​479 0c93e8b Thanks @​james-elicx! - feat: commands for cli actions

  The OpenNext Cloudflare CLI now uses the following commands;

  • build: build the application
  • populateCache: populate either the local or remote cache
  • preview: populate the local cache and start a dev server
  • deploy: populate the remote cache and deploy to production

• #​490 00f6071 Thanks @​vicb! - Drop the deprecated kvCache in favor of kv-cache

Patch Changes

• #​487 0702d2e Thanks @​james-elicx! - feat: support passing the wrangler environment when populating the cache

• #​480 e0ec01d Thanks @​conico974! - fix deduplication for memory queue and add some log

• #​481 9b0db4d Thanks @​conico974! - fix res.revalidate not working in page router api route

• #​484 6ce5643 Thanks @​conico974! - Add sharding replication for the Durable Object Tag Cache

• #​470 2650043 Thanks @​conico974! - feat: add a sharded SQLite Durable object implementation for the tag cache

• #​485 ced7d46 Thanks @​conico974! - add an option for disabling sqlite on the durable object queue

• #​460 60171f5 Thanks @​conico974! - feat: durable object de-duping revalidation queue

• #​497 958f322 Thanks @​vicb! - Switch to bundled middleware

• #​436 86c0139 Thanks @​james-elicx! - feat: auto-populating d1 cache data

• #​464 acfc7f3 Thanks @​conico974! - Implement next mode for d1 tag cache that will reduce write

• #​486 25a8f4c Thanks @​conico974! - auto create table for D1NextModeTagCache

• #​443 54508ff Thanks @​james-elicx! - feat: r2 adapter for the incremental cache

• #​491 e9dc621 Thanks @​vicb! - Serve /cdn-cgi/image/... images in dev

v0.5.12

Compare Source

Patch Changes

• #​467 09c5116 Thanks @​vicb! - Update wrangler dependency

v0.5.11

Compare Source

Patch Changes

• #​455 1d40ab1 Thanks @​vicb! - sync with @opennextjs/[email protected]

• #​453 95caa87 Thanks @​vicb! - fix: Pages router API routes with Next 14

• #​452 161a5f7 Thanks @​vicb! - fix: patch the webpack runtime when there is a single chunk

v0.5.10

Compare Source

Patch Changes

• #​445 6a389fe Thanks @​james-elicx! - fix: deployed worker unable to invoke itself in memory queue

  In deployments, Cloudflare Workers are unable to invoke workers on the same account via fetch, and the recommended way to call a worker is to use a service binding. This change switches to use service bindings for the memory queue to avoid issues with worker-to-worker subrequests.

  To continue using the memory queue, add a service binding to your wrangler config for the binding NEXT_CACHE_REVALIDATION_WORKER.

  {
    "services": [
      {
        "binding": "NEXT_CACHE_REVALIDATION_WORKER",
        "service": "<WORKER_NAME>"
      }
    ]
  }

v0.5.9

Compare Source

Patch Changes

• #​441 4966779 Thanks @​conico974! - Fix for Invariant: renderHTML should not be called in minimal mode

v0.5.8

Compare Source

Patch Changes

• #​431 9ad6714 Thanks @​HyperKiko! - fix pages api routes

  fixed pages api routes by inlining a dynamic require in the NodeModuleLoader class

v0.5.7

Compare Source

Patch Changes

• #​429 1c80772 Thanks @​vicb! - fix import paths in templates

v0.5.6

Compare Source

Patch Changes

• #​412 58b200f Thanks @​dario-piotrowicz! - add defineCloudflareConfig utility

  this change adds a new defineCloudflareConfig utility that developers can use in their open-next.config.ts
  file to easily generate a configuration compatible with the adapter

  Example usage:

  // open-next.config.ts
  import { defineCloudflareConfig } from "@​opennextjs/cloudflare";
  import kvIncrementalCache from "@​opennextjs/cloudflare/kv-cache";
  
  export default defineCloudflareConfig({
    incrementalCache: kvIncrementalCache,
  });

v0.5.5

Compare Source

Patch Changes

• #​417 6d3291f Thanks @​vicb! - define __filename globally

• #​413 01e2bfb Thanks @​ha1fstack! - improve windows support

v0.5.4

Compare Source

Patch Changes

• #​320 ff2dd55 Thanks @​james-elicx! - feat: d1 adapter for the tag cache

• #​409 a604c85 Thanks @​dario-piotrowicz! - make sure that instrumentation files work

  currently instrumentation files
  in applications built using the adapter are ignored, the changes here
  make sure that those are instead properly included in the applications

• #​410 d30424b Thanks @​dario-piotrowicz! - remove eval calls introduced by depd wrapped functions

  Some dependencies of Next.js (raw-body and send) use depd to deprecate some of their functions,
  depd uses eval to generate a deprecated version of such functions, this causes eval warnings in
  the terminal even if these functions are never called, the changes here by patching the depd wrapfunction
  function so that it still retains the same type of behavior but without using eval

• #​404 12d385d Thanks @​dario-piotrowicz! - fix incorrect (sync) getCloudflareContext error message

  currently getCloudflareContext run in sync mode at the top level of a not static route
  gives a misleading error message saying that the function needs to be run in a not static
  route, the changes here correct this error message clarifying that the problem actually is

v0.5.3

Compare Source

Patch Changes

• #​394 1479263 Thanks @​vicb! - fix: improve windows support

v0.5.2

Compare Source

Patch Changes

• #​372 522076b Thanks @​dario-piotrowicz! - add "async mode" to getCloudflareContext

  Add an async option to getCloudflareContext({async}) to run it in "async mode", the difference being that the returned value is a
  promise of the Cloudflare context instead of the context itself

  The main of this is that it allows the function to also run during SSG (since the missing context can be created on demand).

v0.5.1

Compare Source

Patch Changes

• #​467 09c5116 Thanks @​vicb! - Update wrangler dependency

v0.5.0

Compare Source

Minor Changes

• 82bb588: feat: basic in-memory de-duping revalidation queue

Patch Changes

• 2e48d4f: fix: make sure that fetch cache sets are properly awaited

  Next.js does not await promises that update the incremental cache for fetch requests,
  that is needed in our runtime otherwise the cache updates get lost, so this change
  makes sure that the promise is properly awaited via waitUntil

• 0c26049: fix path to file template in open-next.config.ts.

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

v0.4.0

Compare Source

Minor Changes

• 8de2c04: introduce new initOpenNextCloudflareForDev utility and make getCloudflareContext synchronous

  this change introduces a new initOpenNextCloudflareForDev function that must called in the Next.js config file to integrate the Next.js dev server with the open-next Cloudflare adapter.

  Also makes getCloudflareContext synchronous.

  Additionally the getCloudflareContext can now work during local development (next dev) in the edge runtime (including middlewares).

  Moving forward we'll recommend that all applications include the use of the initOpenNextCloudflareForDev utility in their config file (there is no downside in doing so and it only effect local development).

  Example:

  // next.config.mjs
  
  import { initOpenNextCloudflareForDev } from "@​opennextjs/cloudflare";
  
  initOpenNextCloudflareForDev();
  
  /** @​type {import('next').NextConfig} */
  const nextConfig = {};
  
  export default nextConfig;

Patch Changes

• 4ec334a: fix: @​vercel/og failing due to using the node version.

  Patches usage of the @​vercel/og library to require the edge runtime version, and enables importing of the fallback font.

---

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.