Cloudflare Workers URL-Based Module Registry

A dated reading of what is claimed, reported, and independently verified in the current evidence.

Current reading

Readiness band and full integer triple

AI-assisted assembly · derived results

Readiness band

Ready

Primary summary from verified readiness

Evidence strength Weak

Decision

Human editorial judgment · 2026-09-22

Low-friction candidate

Why: It is strictly additive and non-breaking (opt-in flag, legacy registry stays the default for everyone else), directly benefits every Cloudflare-Workers-hosted Pragma.Vision platform (64 MiB uncompressed bundle ceiling on all plans, lazy compilation, shared isolate code caches, cleaner node: compat and import.meta), and costs nothing extra under Rule #9's provisioned Workers Paid plan — but the September 2026 stable announcement has limited independent field validation, so full/default adoption should wait for broader field evidence and the docs to catch up.
Next: Pilot the `new_module_registry` compatibility flag on one low-traffic, non-Rule-#29 Worker behind the existing gradual-deployment canary path (Rule #31); verify import.meta/node: built-in behavior, require(esm) semantics, and error-class consistency against current bundles before considering it for any Rule #29-protected surface; re-check once the flag lands in the official compatibility-flags reference docs.

Constraints

No named blocker is present in the current public projection.

Evidence summary

AI-assisted assembly

Counts and dates only. Raw signals, private excerpts, trust records, and internal corpus material are not published here.

Publication record

Initial public reading