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

@opennextjs/[email protected]

Patch Changes

• 66ba0ff: enhancement: Expand missing next.config error message

  Found out that next dev can run the a Next.js app without next.config but
  if we are using the adapter we throw an error if we don't find the config.
  So expanded the error for users.

@opennextjs/[email protected]

Minor Changes

• 87f4fb5: feat: configure kv binding name with env var

  The Workers KV binding used in the Next.js cache handler can be given a custom name with the __OPENNEXT_KV_BINDING_NAME environment variable at build-time, instead of defaulting to NEXT_CACHE_WORKERS_KV.

Patch Changes

• 83abcfe: refactor: retrieve cache handler kv instance inside constructor

  The cache handler was retrieving it's KV instance as a static property on the class that was defined at some point during the execution of the Next.js server. This moves the retrieval of the KV instance to happen inside the constructor for the class, so that it is retrieved during instantiation instead.

@opennextjs/[email protected]

Patch Changes

• a99cd1e: ci: actually publish updates packages to npm