@opennextjs/cloudflare@0.5.4

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

@opennextjs/cloudflare@0.5.3

Patch Changes

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

@opennextjs/cloudflare@0.5.2

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).

@opennextjs/cloudflare@0.5.1

Patch Changes

• ad895ed: fix: vercel og patch not moving to right node_modules directory

  There are two separate places where the node_modules could be. One is a package-scoped node_modules which does not always exist - if it doesn't exist, the server functions-scoped node_modules is used.

@opennextjs/cloudflare@0.5.0

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.

@opennextjs/cloudflare@0.4.8

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

@opennextjs/cloudflare@0.4.7

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

@opennextjs/cloudflare@0.4.6

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.

@opennextjs/cloudflare@0.4.5

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.

@opennextjs/cloudflare@0.4.4

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