// AI Platform Drift
Cloudflare Workers switches to new module registry on 17 November 2026
Cloudflare developer changelog · published 2026-11-11 04:55 UTC
WHAT CHANGEDStarting 17 November 2026, JavaScript Workers with compatibility date 2026-11-17 or later will use the new module registry by default. The new_module_registry flag will no longer be required for these dates. The new registry changes how require() and import.meta work: require() can load ES modules but fails if the module or its dependencies use top-level await, and import.meta.resolve() becomes available. The new registry also rejects invalid import attributes.
WHY IT MATTERSExisting Workers that update their compatibility date to 2026-11-17 or later will automatically switch registries, which can break code that uses top-level await in modules loaded via require(), relies on invalid import attributes, or depends on legacy require() behavior. Workers that do not explicitly opt into the legacy registry will fail at runtime if they hit these incompatibilities.
WHAT TO DOBefore updating any Worker's compatibility date to 2026-11-17 or later, audit dependencies for top-level await in modules you require() and for invalid import attributes. Test with the new_module_registry flag added to your current compatibility date. If you must preserve legacy behavior after updating the date, add the legacy_module_registry flag to your Worker configuration.
ACT-BY DATE PASSED — this item's act-by date, 2026-11-17, is before this page was generated 2026-11-21 (UTC). Check the primary source before acting on it.
Model-reported confidence 95% (not measured accuracy)
Primary source ↗
written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Workers - Workers will use the new module registry by default on November 17 +https://developers.cloudflare.com/changelog/post/2026-11-02-module-registry-default/ +Mon, 02 Nov 2026 00:00:00 GMT + +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. +The module registry finds and loads JavaScript modules in your Worker. We announced the new registry in September 2026 ↗︎. It improves compatibility with JavaScript standards and Node.js. In Workers using Node.js compatibility, you can use require() to load ES modules. The module and its dependencies must not use top-level await. +You can also use import.meta to get information about the current module and find the URL of another module without loading it: +src/index.jsjsexport default { +fetch() { +return Response.json({ +moduleUrl: import.meta.url, +isEntrypoint: import.meta.main, +helperUrl: import.meta.resolve("./helper.js"), +}); +}, +};src/index.tstsexport default { +fetch(): Response { +return Response.json({ +moduleUrl: import.meta.url, +isEntrypoint: import.meta.main, +helperUrl: import.meta.resolve("./helper.js"), +}); +}, +} satisfies ExportedHandler; +When deployed with src/index.ts as the unbundled entrypoint, isEntrypoint is true. helperUrl is a URL within your Worker bundle. Resolving the URL does not check whether the module exists or load it over the network. Build tools may transform import.meta. To try this example directly, refer to unbundled deployments. +Existing Workers keep their current behavior until you change their compatibility date or flags. To try the new registry before November 17, keep your current date and add new_module_registry to your compatibility flags. +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 with a compatibility date of 2026-11-17 or later, add legacy_module_registry. +For migration details, refer to the new module registry compatibility flag, bundling documentation, and Node.js compatibility documentation.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
| triage verdict | MATERIAL at 0.95, needed 0.5 |
|---|---|
| triage reasoning | Default module registry changes on a specific date; existing Workers must take action to preserve current behavior. |
| signals | future date: November 17, 2026 · breaking change: default behavior shift for Workers with compatibility date 2026-11-17+ · flag removal: new_module_registry flag no longer required after date · migration required: existing Workers must opt-in to legacy_module_registry to preserve old behavior · behavioral change: require() and import.meta now work differently · new constraint: top-level await now rejected in modules |
| suppression | — |
| triage model | anthropic/claude-haiku-4.5 ($0.00000) |
| writer model | anthropic/claude-sonnet-4.5 ($0.00000) |