# Cloudflare Workers switch to a new module registry and Request.signal by default for the 2026-11-17 compatibility date

> Four runtime defaults change today for Workers that move their compatibility date forward. Deployed Workers are untouched, but require() with top-level await and invalid import attributes now fail under the new registry.

Source: Promptea — https://www.promptea.me/en/blog/cloudflare-workers-new-defaults-compatibility-date-2026-11-17 · Language: English · Last updated: 2026-11-17

Published: 2026-11-17 · Event date: 2026-11-17 · Category: cloud · Author: Promptea Editorial

**Summary:** Starting today, Cloudflare Workers with a compatibility date of 2026-11-17 or later use the new module registry, receive a Request.signal that fires on client disconnect, and get two changed cache and stream defaults. Existing Workers keep their behavior until their date changes; each change has an opt-out flag.

As of today, November 17, 2026, Cloudflare Workers that set a compatibility date of 2026-11-17 or later run with four changed runtime defaults. Cloudflare announced the two largest on its developer changelog on November 2: JavaScript Workers now load code through the new module registry, and incoming requests now carry a Request.signal that fires when the client disconnects. The Workers compatibility flags documentation lists two more defaults with the same date, one for caching and one for streams. All three sources cited here are Cloudflare's own.

Nothing changes for a deployed Worker on its own. Cloudflare says existing Workers keep their current behavior until their compatibility date or flags change. The changes apply the first time a team moves the compatibility_date in its configuration to today or later, which is what a new project created from today on will usually get.

## What changes for people who build on Workers

- New module registry: JavaScript Workers use the new registry by default. With Node.js compatibility enabled, require() can load ES modules, as long as neither the module nor its dependencies use top-level await. import.meta exposes the module's url, whether it is the entrypoint (main), and a resolve() method. Python Workers keep the legacy registry.
- Request.signal: incoming Request objects provide an AbortSignal that fires an abort event when the client disconnects. Passing request.signal to an outgoing fetch() cancels that upstream request when the user leaves.
- cache_option_preserves_cache_control: according to the flags documentation, setting the Request cache option to no-cache or no-store no longer overrides the Cache-Control header of the origin's response when Cloudflare caches it.
- pipe_to_backward_propagation: pipeTo() and pipeThrough() into a JavaScript-created WritableStream now propagate errors and closure from the destination back to the source, so the pipe's promise can reject where it used to resolve.

## What can break, and how to opt out

Cloudflare names two breaking behaviors for the module registry: it rejects invalid import attributes, and require() fails if the module or any of its dependencies use top-level await. The changelog asks developers to check their dependencies for both before updating the date. To keep the old loader with a newer date, add the legacy_module_registry flag. Request.signal can be turned off with disable_request_signal, and the two stream and cache defaults have their own opt-out flags: no_pipe_to_backward_propagation and cache_option_overrides_cache_control. Teams that want to test early on an older date can add new_module_registry or enable_request_signal instead.

For AI features the Request.signal change is the practical one. A Worker that proxies a long, streamed model response can now stop the upstream call when the person closes the tab, instead of paying for tokens nobody reads. Cloudflare's changelog does not mention AI or streaming use cases; that is an application of the documented behavior, and it only works if the code passes the signal on, because Cloudflare says request_signal_passthrough is not enabled by this change.

## What the announcement does not say

Cloudflare does not say how many Workers are expected to hit the import-attribute or top-level-await errors, and the Request.signal entry does not discuss breakage at all. The cache and stream defaults appear only in the compatibility flags documentation, without a changelog post of their own. No independent coverage of the change was found at the time of writing.

## Key takeaways

- Four Workers defaults change for compatibility date 2026-11-17 or later; existing Workers are unaffected until their date or flags change.
- The new module registry rejects invalid import attributes and fails require() when a dependency uses top-level await; legacy_module_registry opts out.
- Request.signal now fires on client disconnect; disable_request_signal opts out, and the signal must be passed on explicitly.

## Why this matters

- Bumping compatibility_date is routine maintenance, and from today it can surface import-attribute and top-level-await errors in dependencies that previously loaded fine.
- Request.signal by default lets Workers that proxy long or streamed responses, such as LLM output, cancel upstream calls when the user leaves, if the code passes the signal on.
- Workers now load ES modules through require() under Node.js compatibility, which removes a common friction point when porting npm packages.

## Sources

- [Workers will use the new module registry by default on November 17](https://developers.cloudflare.com/changelog/post/2026-11-02-module-registry-default/) — Cloudflare (primary source), accessed 2026-11-17
- [Request.signal will be enabled by default in Workers on November 17](https://developers.cloudflare.com/changelog/post/2026-11-02-request-signal-default/) — Cloudflare (primary source), accessed 2026-11-17
- [Compatibility flags · Cloudflare Workers docs](https://developers.cloudflare.com/workers/configuration/compatibility-flags/) — Cloudflare (primary source), accessed 2026-11-17

*Researched with AI assistance and verified against primary sources before publishing. Every claim links to where it came from.*
