@opennextjs/[email protected]

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

@opennextjs/[email protected]

Patch Changes

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

@opennextjs/[email protected]

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

@opennextjs/[email protected]

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>"
      }
    ]
  }

@opennextjs/[email protected]

Patch Changes

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

@opennextjs/[email protected]

Patch Changes

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

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

@opennextjs/[email protected]

Patch Changes

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

@opennextjs/[email protected]

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,
  });

@opennextjs/[email protected]

Patch Changes

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

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

@opennextjs/[email protected]

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