- JavaScript Workers with compatibility date ≥ 2026‑11‑17 will use the new module registry by default, removing the need for the `new_module_registry` flag.
- The new registry adds Node.js‑compatible module loading (e.g., `require()` for ES modules) but disallows top‑level await and rejects invalid import attributes; Python Workers remain on the legacy registry.
- Existing Workers keep current behavior until their compatibility date or flags change, and you can opt‑in early or stay on the legacy registry with `legacy_module_registry`.