Update recently added compatibility flags

Author: jasnell

src/content/compatibility-flags/cache-api-request-cf-overrides-cache-rules.md

@@ -0,0 +1,16 @@
+---
+_build:
+  publishResources: false
+  render: never
+  list: never
+
+name: "Cache API request `cf` overrides cache rules"
+sort_date: "2025-05-19"
+enable_date: "2025-05-19"
+enable_flag: "cache_api_request_cf_overrides_cache_rules"
+disable_flag: "no_cache_api_request_cf_overrides_cache_rules"
+---
+
+When `cache_api_request_cf_overrides_cache_rules` is enabled, cache settings specified in the `cf` object of a request passed to the [Cache API](/workers/runtime-apis/cache/) will override cache rules. This applies only to user-owned or grey-clouded sites.
+
+This is the Cache API counterpart to the [`request_cf_overrides_cache_rules`](/workers/configuration/compatibility-flags/#fetch-api-request-cf-overrides-cache-rules) flag, which applies to the `fetch()` API.

src/content/compatibility-flags/enable-fast-jsg-struct.md

@@ -0,0 +1,18 @@
+---
+_build:
+  publishResources: false
+  render: never
+  list: never
+
+name: "Enable fast JSG struct optimization"
+sort_date: "2025-12-03"
+enable_date: "2025-12-03"
+enable_flag: "enable_fast_jsg_struct"
+disable_flag: "disable_fast_jsg_struct"
+---
+
+When `enable_fast_jsg_struct` is enabled, internal struct types used by Workers runtime APIs are constructed using a more efficient pattern that reduces object creation time.
+
+However, optional fields will be explicitly set to `undefined` rather than being omitted from the object entirely, which is an observable behavior change. Code that checks for the presence of a property using `"key" in obj` or `Object.hasOwn(obj, "key")` may behave differently, since optional fields that were previously absent will now be present with a value of `undefined`.
+
+To check for a value, prefer `obj.key !== undefined` over `"key" in obj`.

src/content/compatibility-flags/enable-global-performance-classes.md

@@ -0,0 +1,18 @@
+---
+_build:
+  publishResources: false
+  render: never
+  list: never
+
+name: "Enable global Performance classes"
+sort_date: "2026-03-17"
+enable_date: "2026-03-17"
+enable_flag: "enable_global_performance_classes"
+disable_flag: "disable_global_performance_classes"
+---
+
+When `enable_global_performance_classes` is enabled, the following classes are available on the global scope: `PerformanceEntry`, `PerformanceMark`, `PerformanceMeasure`, `PerformanceResourceTiming`, `PerformanceObserver`, and `PerformanceObserverEntryList`.
+
+These classes are also implicitly enabled by the `enable_nodejs_perf_hooks_module` flag.
+
+This flag is automatically enabled for Workers using a compatibility date of 2026-03-17 or later when [`nodejs_compat`](/workers/runtime-apis/nodejs/) is enabled.

src/content/compatibility-flags/enable-nodejs-child-process-module.md

@@ -0,0 +1,18 @@
+---
+_build:
+  publishResources: false
+  render: never
+  list: never
+
+name: "Enable `node:child_process` module"
+sort_date: "2026-03-17"
+enable_date: "2026-03-17"
+enable_flag: "enable_nodejs_child_process_module"
+disable_flag: "disable_nodejs_child_process_module"
+---
+
+The `enable_nodejs_child_process_module` flag enables the `node:child_process` module stub in Workers.
+
+This flag is automatically enabled for Workers using a compatibility date of 2026-03-17 or later when [`nodejs_compat`](/workers/runtime-apis/nodejs/) is enabled.
+
+See the [Node.js documentation](https://nodejs.org/docs/latest/api/child_process.html) for more details about the `node:child_process` API.

src/content/compatibility-flags/enable-nodejs-cluster-module.md

@@ -0,0 +1,18 @@
+---
+_build:
+  publishResources: false
+  render: never
+  list: never
+
+name: "Enable `node:cluster` module"
+sort_date: "2025-12-04"
+enable_date: "2025-12-04"
+enable_flag: "enable_nodejs_cluster_module"
+disable_flag: "disable_nodejs_cluster_module"
+---
+
+The `enable_nodejs_cluster_module` flag enables the `node:cluster` module stub in Workers.
+
+This flag is automatically enabled for Workers using a compatibility date of 2025-12-04 or later when [`nodejs_compat`](/workers/runtime-apis/nodejs/) is enabled.
+
+See the [Node.js documentation](https://nodejs.org/docs/latest/api/cluster.html) for more details about the `node:cluster` API.

src/content/compatibility-flags/enable-nodejs-console-module.md

@@ -0,0 +1,18 @@
+---
+_build:
+  publishResources: false
+  render: never
+  list: never
+
+name: "Enable `node:console` module"
+sort_date: "2025-09-21"
+enable_date: "2025-09-21"
+enable_flag: "enable_nodejs_console_module"
+disable_flag: "disable_nodejs_console_module"
+---
+
+The `enable_nodejs_console_module` flag enables the `node:console` module in Workers.
+
+This flag is automatically enabled for Workers using a compatibility date of 2025-09-21 or later when [`nodejs_compat`](/workers/runtime-apis/nodejs/) is enabled.
+
+See the [Node.js documentation](https://nodejs.org/docs/latest/api/console.html) for more details about the `node:console` API.

src/content/compatibility-flags/enable-nodejs-dgram-module.md

@@ -0,0 +1,18 @@
+---
+_build:
+  publishResources: false
+  render: never
+  list: never
+
+name: "Enable `node:dgram` module"
+sort_date: "2026-01-29"
+enable_date: "2026-01-29"
+enable_flag: "enable_nodejs_dgram_module"
+disable_flag: "disable_nodejs_dgram_module"
+---
+
+The `enable_nodejs_dgram_module` flag enables the `node:dgram` module stub in Workers.
+
+This flag is automatically enabled for Workers using a compatibility date of 2026-01-29 or later when [`nodejs_compat`](/workers/runtime-apis/nodejs/) is enabled.
+
+See the [Node.js documentation](https://nodejs.org/docs/latest/api/dgram.html) for more details about the `node:dgram` API.

src/content/compatibility-flags/enable-nodejs-domain-module.md

@@ -0,0 +1,18 @@
+---
+_build:
+  publishResources: false
+  render: never
+  list: never
+
+name: "Enable `node:domain` module"
+sort_date: "2025-12-04"
+enable_date: "2025-12-04"
+enable_flag: "enable_nodejs_domain_module"
+disable_flag: "disable_nodejs_domain_module"
+---
+
+The `enable_nodejs_domain_module` flag enables the `node:domain` module stub in Workers. Note that `node:domain` is deprecated in Node.js itself.
+
+This flag is automatically enabled for Workers using a compatibility date of 2025-12-04 or later when [`nodejs_compat`](/workers/runtime-apis/nodejs/) is enabled.
+
+See the [Node.js documentation](https://nodejs.org/docs/latest/api/domain.html) for more details about the `node:domain` API.

src/content/compatibility-flags/enable-nodejs-fs-module.md

@@ -0,0 +1,18 @@
+---
+_build:
+  publishResources: false
+  render: never
+  list: never
+
+name: "Enable `node:fs` module"
+sort_date: "2025-09-15"
+enable_date: "2025-09-15"
+enable_flag: "enable_nodejs_fs_module"
+disable_flag: "disable_nodejs_fs_module"
+---
+
+The `enable_nodejs_fs_module` flag enables the `node:fs` module in Workers.
+
+This flag is automatically enabled for Workers using a compatibility date of 2025-09-15 or later when [`nodejs_compat`](/workers/runtime-apis/nodejs/) is enabled.
+
+See the [Node.js documentation](https://nodejs.org/docs/latest/api/fs.html) for more details about the `node:fs` API.

src/content/compatibility-flags/enable-nodejs-global-timers.md

@@ -0,0 +1,18 @@
+---
+_build:
+  publishResources: false
+  render: never
+  list: never
+
+name: "Enable Node.js-compatible global timers"
+sort_date: "2026-02-10"
+enable_date: "2026-02-10"
+enable_flag: "enable_nodejs_global_timers"
+disable_flag: "no_nodejs_global_timers"
+---
+
+When `enable_nodejs_global_timers` is enabled, `setTimeout`, `setInterval`, `clearTimeout`, and `clearInterval` return Node.js-compatible `Timeout` objects with methods like `refresh()`, `ref()`, `unref()`, and `hasRef()`, matching the behavior of `node:timers`.
+
+This flag requires [`nodejs_compat`](/workers/runtime-apis/nodejs/) to be enabled and is automatically enabled for Workers using a compatibility date of 2026-02-10 or later when `nodejs_compat` is enabled.
+
+See the [Node.js documentation](https://nodejs.org/docs/latest/api/timers.html) for more details about the timer APIs.