Cloudflare Workers just got a massive Node.js compatibility boost via a rewritten

The new new_module_registry compatibility flag essentially closes the gap between the Workers runtime and actual Node.js behavior. It's not just about adding more APIs—though they've now removed the compressed bundle size limit, allowing up to 64 MiB on all plans—it's about how the runtime actually handles loading, caching, and resolving ESM, CommonJS, and WASM. If you're deploying complex Node apps that rely on dynamic imports or specific module resolution logic, this is the fix you've been waiting for.

How do I actually enable this?

You can't just "update" your runtime; you have to explicitly opt-in via your configuration. Add the following to your wrangler.toml file:

compatibility_flags = [ "new_module_registry" ]

Once deployed, you'll notice a few immediate changes. Things like import.meta.url, import.meta.main, and import.meta.resolve() finally work as expected. More importantly, node: built-ins now resolve to the same module instance regardless of the path used to reach them, which prevents the nightmare of having multiple instances of a singleton library causing state bugs.

What actually changed under the hood?

For a long time, Cloudflare relied heavily on bundling (via esbuild in Wrangler) to flatten your entire dependency tree into a single massive script before it ever hit the runtime. This is why you might see bundles with hundreds of thousands of lines of code. The runtime didn't have to do much "resolving" because the bundler had already done it.

The problem was that this approach breaks any code that expects a real module graph. If a library used import.meta.resolve() to find a sibling file, it would crash because the runtime didn't recognize the URL.

By rewriting the registry in workerd, Cloudflare has moved closer to the V8 module API standards. This means:

• Lazy Compilation: Modules only compile when they are first imported (statically or dynamically), which should theoretically improve cold start performance for larger apps.
• Strict Validation: Import attributes, like with { type: 'json' }, are now correctly validated.
• CJS/ESM Interop: Using require() on an ES module now follows the actual Node.js require(esm) rules rather than a "best guess" implementation.
• WASM Support: WebAssembly modules now support source phase imports.

When should you NOT use this?

If your Worker is a simple "Hello World" or a basic API proxy with zero dependencies, you won't notice a difference. However, if you are using the Cloudflare Vite plugin (which uses Rolldown), you're already emitting a module graph rather than a single flat file. In that scenario, this new registry is almost mandatory to ensure that code splitting and dynamic imports behave the same way in production as they do in your local dev environment.

The most checkable win here is the 64 MiB bundle limit. If you've previously hit the compressed size ceiling while trying to deploy a heavy Node.js framework or a large set of dependencies, enabling this flag and deploying again is the first thing you should try.