Provider changes/CloudflareCLOUDFLARE · VERIFIED CHANGE

Workers compatibility dates of 2026-11-17 or later enable the new JavaScript module registry

Workers compatibility dates of 2026-11-17 or later enable the new JavaScript module registry and Request.signal disconnection events by default. The registry changes import validation and require() behavior; existing Workers retain current behavior until their compatibility date or flags change.

Verified Nov 2, 20262 official sources

Mentioned in the evidence

  • Cloudflare Workers
  • JavaScript Workers module registry
  • Workers Request.signal

Official sources

  • Cloudflare developer changelog (changelog) ↗
    Before updating, check your dependencies for invalid import attributes and changes to require() behavior. The new registry rejects invalid import attributes. Calls to require() also fail if the module or any of its dependencies use top-level await. To keep the legacy registry
  • Cloudflare developer changelog (changelog) ↗
    Starting November 17, 2026, JavaScript Workers with a compatibility date of 2026-11-17 or later will use the new module registry by default. You will no longer need the new_module_registry flag for these dates. Python Workers keep using the legacy registry.

This is a global change, verified against Cloudflare’s own sources. It is not an assessment of your systems or your impact.

A global change is not your impact.

Auterim checks your confirmed dependencies and can verify repository references when GitHub is connected.