@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

@opennextjs/[email protected]

Patch Changes

• d488d86: fix: exclude .env.local files for test mode

  Aligns with the Next.js behavior of not extracting variables from the .env.local file in test environments.

• 0ee77b2: fix the city header encoding

  By pulling opennextjs/opennextjs-aws#688

• 4b6a50b: check and create a wrangler.json file for the user in case a wrangler.(toml|json|jsonc) file is not already present

  also introduce a new --skipWranglerConfigCheck cli flag and a SKIP_WRANGLER_CONFIG_CHECK
  environment variable that allows users to opt out of the above check (since developers might
  want to use custom locations for their config files)

• 7654867: bump "@opennextjs/aws dependency to https://pkg.pr.new/@opennextjs/aws@686

@opennextjs/[email protected]

Patch Changes

• b3949ce: fix: delete init.cache rather than assign undefined

  Assigning undefined to init.cache throws when using NextAuth

• 12a1f75: update location of output path in success message

@opennextjs/[email protected]

Patch Changes

• c0c1d04: fix: CustomRequest instantiation

  In some cases some request properties would not be initialized (i.e. method, headers, ...)
  The bug was caused by the processing the init in the CustomRequest class.
  The bug was tigerred when using clerk.

@opennextjs/[email protected]

Patch Changes

• f60a326: fix: cleanup dependencies

@opennextjs/[email protected]

Minor Changes

• ca2d452: feat: rename the binary from "cloudflare" to "opennextjs-cloudflare"

  BREAKING CHANGE:
  After this change the old way of running the tool (e.g. pnpm cloudflare) no longer works.
  Going forward use the new binary name (e.g. pnpm opennextjs-cloudflare).

  See #161

• Add support for middleware, loading .env* files, ...

@opennextjs/[email protected]

Patch Changes

• 5bceecc: example: Add vercel blog starter

  Update the examples with vercel blog starter and adapt it to run on cf workers

@opennextjs/[email protected]

Minor Changes

• 6acf0fd: feat: cli arg to disable minification

  The cache handler currently forces minification. There is now a CLI arg to disable minification for the build. At the moment, this only applies to the cache handler but may be used for other parts of the build in the future when minification is introduced to them. By default, minification is enabled, but can be disabled by passing --noMinify.