Repository navigation
Enable the new module registry by default from 2026-11-01 - #7799
Draft
irvinebroque wants to merge 1 commit into
Draft
irvinebroque wants to merge 1 commit into
irvinebroque wants to merge 1 commit into
Conversation
irvinebroque
force-pushed
the
codex/module-registry-default-nov-2026
branch
from
October 17, 2026 15:25
44e588e to
468f632
Compare
2 tasks done
irvinebroque
force-pushed
the
codex/module-registry-default-nov-2026
branch
2 times, most recently
from
October 17, 2026 15:41
4442cca to
f51bc6c
Compare
Compatibility decision: use the new JavaScript module registry for compatibility dates on or after 2026-11-01, including import.meta, URL-based resolution, import attribute validation, and Node.js require(esm) semantics. Earlier dates retain the opt-in behavior and legacy_module_registry remains an opt-out. Python Workers retain the legacy registry. Allow the scheduled Sunday date in the existing weekday guard. Remove the standalone server experimental-mode restriction so date-enabled Workers can start without --experimental.
irvinebroque
force-pushed
the
codex/module-registry-default-nov-2026
branch
from
October 17, 2026 15:58
f51bc6c to
9113db3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
JavaScript Workers currently require
new_module_registryto use URL-based module resolution,import.meta, validated import attributes, and the newrequire(esm)semantics. Make the registry the default for compatibility dates on or after 2026-11-01. Earlier dates retain their current behavior,legacy_module_registryremains an opt-out, and Python Workers retain the legacy registry.Remove the standalone server requirement for
--experimentalso Workers using the default registry can start normally. Preserve the requested Sunday date with a flag-specific exception to the existing weekday guard. The compatibility decision is recorded in the commit message.The companion docs PR includes an October 17 advance announcement, an example, migration guidance, and a link to the September 2026 blog announcement. Publish the docs before November 1.
Validation: targeted
just formatandgit diff --checkpass.The compatibility-docs CI check requires an approving review on the companion docs PR (or its merge to production). That review is pending.