@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

@opennextjs/[email protected]

Patch Changes

• 05ee8d4: fix: invalid paths in windows bundles.

@opennextjs/[email protected]

Patch Changes

• 41c55a8: Add support for specifying wrangler environment when using next dev so that bindings and vars are properly loaded. This can be specified with the env variable NEXT_DEV_WRANGLER_ENV.
• 2e13de2: fix broken patchRequireReactDomServerEdge patch

@opennextjs/[email protected]

Patch Changes

• 9ab86d4: fix: host not included in route handler urls

  Next.js was unable to re-construct the correct URLs for the request in a route handler due to being unable to retrieve the hostname. This was due to the internal Next.js option trustHostHeader being disabled in OpenNext when there is external middleware - this option is needed for the Next.js server in our environment.

@opennextjs/[email protected]

Patch Changes

• 77e31d5: update the patchExceptionBubbling patch
• dbcc4be: patch require("react-dom/server.edge") calls in pages.runtime.prod.js so that they are try-catched
• 632a7d7: show error on Next.js versions older than v14