Minor Changes
-
#848
f80c801
Thanks @sommeeeer! - Ensure that the initial request.signal is passed to the wrapperrequest.signal.onabort
is 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 thatAbortSignal
through thestreamCreator
in 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.signal
to the handler. You also need to enable the compatibility flagenable_request_signal
to use this feature.For example:
// Before: return handler(reqOrResp, env, ctx); // After: return handler(reqOrResp, env, ctx, request.signal);
-
#850
ce5c7b4
Thanks @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
bypassTagCacheOnCacheHit
option is being added to theRegionalCache
class.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, });