@opennextjs/[email protected]

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/[email protected]

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/[email protected]

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/[email protected]

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

@opennextjs/[email protected]

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)

@opennextjs/[email protected]

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

@opennextjs/[email protected]

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

@opennextjs/[email protected]

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.

@opennextjs/[email protected]

Patch Changes

• 48f863f: fix: do not require caniuse-lite

  caniuse-lite is an optional dependency.

• 27ab1ab: refactor: use the new regex utility for constructing cross-platform paths

@opennextjs/[email protected]

Patch Changes

• 67fafeb: fix top level awaits not working in middlewares by bumping the @opennextjs/aws package