Releases: opennextjs/opennextjs-cloudflare
@opennextjs/[email protected]
@opennextjs/[email protected]
Patch Changes
-
#888
51322a8Thanks @james-elicx! - fix: remote flag not working for preview command's cache populationPreviously, passing the
--remoteflag when runningopennextjs-cloudflare preview --remotewould not result in the remote preview binding being populated, and would throw errors due to a missing preview flag when populating Workers KV. The remote flag is now supported for the cache popoulation step when running the preview command.opennextjs-cloudflare preview --remotewill populate the remote binding for the preview ID specified in your Wrangler config.opennextjs-cloudflare previewwill continue to populate the local binding in your Wrangler config.
@opennextjs/[email protected]
Patch Changes
-
#892
1ee505fThanks @vicb! - Bump @opennextjs/aws to 3.7.7See details at https://github.com/opennextjs/opennextjs-aws/releases/tag/v3.7.7
@opennextjs/[email protected]
@opennextjs/[email protected]
@opennextjs/[email protected]
Minor Changes
- #862
728ad99Thanks @james-elicx! - feat: support for a custom OpenNext config path with the--openNextConfigPathflag
Patch Changes
-
#872
dc76d6eThanks @alex-all3dp! - Fix check for missing CACHE_PURGE_ZONE_ID -
#862
728ad99Thanks @james-elicx! - refactor: deprecate usage of the--configPathflag for the Wrangler config, in favour of the--configflag.
@opennextjs/[email protected]
@opennextjs/[email protected]
Minor Changes
-
#848
f80c801Thanks @sommeeeer! - Ensure that the initial request.signal is passed to the wrapperrequest.signal.onabortis now supported in route handlers. It requires that the signal from the original worker's request is passed to the handler. It will then pass along thatAbortSignalthrough thestreamCreatorin the wrapper. This signal will destroy the response sent to NextServer when a client aborts, thus triggering the signal in the route handler.See the changelog in Cloudflare here.
Note:
If you have a custom worker, you must update your code to pass the originalrequest.signalto the handler. You also need to enable the compatibility flagenable_request_signalto use this feature.For example:
// Before: return handler(reqOrResp, env, ctx); // After: return handler(reqOrResp, env, ctx, request.signal);
-
#850
ce5c7b4Thanks @dario-piotrowicz! - Add option for regional cache to skip tagCache on cache hitsWhen the tag regional cache finds a value in the incremental cache, checking such value in the tagCache can be skipped, this helps reducing response times at the tradeoff that the user needs to either use the automatic cache purging or manually purge the cache when appropriate. For this the
bypassTagCacheOnCacheHitoption is being added to theRegionalCacheclass.Example:
import { defineCloudflareConfig } from "@opennextjs/cloudflare"; import d1NextTagCache from "@opennextjs/cloudflare/overrides/tag-cache/d1-next-tag-cache"; import memoryQueue from "@opennextjs/cloudflare/overrides/queue/memory-queue"; import r2IncrementalCache from "@opennextjs/cloudflare/overrides/incremental-cache/r2-incremental-cache"; import { withRegionalCache } from "@opennextjs/cloudflare/overrides/incremental-cache/regional-cache"; export default defineCloudflareConfig({ incrementalCache: withRegionalCache(r2IncrementalCache, { mode: "long-lived", bypassTagCacheOnCacheHit: true, }), tagCache: d1NextTagCache, queue: memoryQueue, });
Patch Changes
-
#858
7233c03Thanks @vicb! - bump @opennextjs/aws to 3.7.6See the changes at opennextjs/opennextjs-aws@v3.7.4...v3.7.6
-
#857
b8b38eeThanks @vicb! - Clean output directory beforenext build
@opennextjs/[email protected]
@opennextjs/[email protected]
Patch Changes
-
#838
90f451dThanks @conico974! - bump @opennextjs/aws to 3.7.4See details at https://github.com/opennextjs/opennextjs-aws/releases/tag/v3.7.4
-
#833
c9705e5Thanks @sommeeeer! - Update the patches to support Next.js 15.4"