Skip to content

Releases: opennextjs/opennextjs-cloudflare

@opennextjs/[email protected]

09 Jan 10:48
6e51aa2
Compare
Choose a tag to compare

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]

06 Jan 13:39
8e4013f
Compare
Choose a tag to compare

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]

28 Dec 15:31
89bda8c
Compare
Choose a tag to compare

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]

23 Dec 10:43
b7a0720
Compare
Choose a tag to compare

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]

21 Dec 09:18
efae3ab
Compare
Choose a tag to compare

Patch Changes

  • f60a326: fix: cleanup dependencies

@opennextjs/[email protected]

20 Dec 15:21
bbba0a8
Compare
Choose a tag to compare

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]

14 Oct 06:01
Compare
Choose a tag to compare

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]

11 Oct 18:07
e7311df
Compare
Choose a tag to compare

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]

10 Oct 19:13
652c1d1
Compare
Choose a tag to compare

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]

10 Oct 06:38
c63b16a
Compare
Choose a tag to compare

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.