ST-2026-203 · Runtimes & developer platforms
Cloudflare Workers enables Node.js compatibility by default for compatibility dates from 2026-08-04
Cloudflare changed Workers compatibility behavior on 4 August 2026 so nodejs_compat and nodejs_compat_v2 behavior is enabled by default for compatibility dates of 2026-08-04 or later, while earlier dates remain unaffected and explicit opt-out flags are available.
Previous state
Workers projects had to opt into Node.js compatibility behavior with compatibility flags rather than receiving the announced behavior by default from a compatibility-date threshold.
Current state
Workers using a compatibility date of 2026-08-04 or later receive nodejs_compat and nodejs_compat_v2 behavior by default; earlier dates are unaffected and explicit no_nodejs_compat flags can disable the behavior.
Affected users
Who needs to care
Cloudflare Workers developers selecting or advancing a compatibility date to 2026-08-04 or later.
Required response
What to do
Test dependencies and runtime behavior before advancing a Worker's compatibility date; use the documented opt-out flags if Node.js compatibility should remain disabled.
Evidence boundary
What the source does not prove
The source proves the default compatibility behavior for dates of 2026-08-04 or later. It does not change Workers pinned to earlier compatibility dates and does not establish universal parity with every Node.js API.
Lifecycle history
Dated event sequence
- Node.js compatibility becomes default at the new date threshold
Cloudflare enabled nodejs_compat and nodejs_compat_v2 behavior by default for Workers compatibility dates of 2026-08-04 or later.
Evidence ledger
First-party sources
- 01Cloudflare — Node.js compatibility is now enabled by default
Official Cloudflare changelog · 2026-08-04
Open official source ↗