Nitro has introduced an experimental (opt-in) way to generate/extend wrangler.toml for cloudflare deployments (#2353, #2355) (However, overwriting the user config is not ideal or recommended, so it remain experimental)

The end goal is to leverage Cloudflare platform features such as Node compat v2 (hybrid) and Async Context with zero-config and ensure we can reliably enable these features.

Thanks to the huge huge efforts and collab with the Cloudflare team and @petebacondarwin, a new solution (~> cloudflare/workers-sdk#7442) is coming to allow frameworks like Nitro to generate a merged wrangler.toml in dist and config that redirects/points wrangler CLI and pages CI to it.

Docs: https://developers.cloudflare.com/workers/wrangler/configuration/#generated-wrangler-configuration

Remarks

• cloudflare.noWranglerDeployConfig: true can be used to opt-out from generating deploy-config in .wrangler/deploy/config.json
• User config wrangler.toml|json is read and always merged with the highest precedence
• Modules and frameworks can extend config by extending cloudflare.wrangler object
• Nitro preset adds defaults
  • compatibility_date defaults to compatibilityDate from framework config
  • compatibility_flags defaults to ["nodejs_compat", "no_nodejs_compat_v2"]

Pages

pnpm nitro build playground --preset cloudflare_pages

dist/_worker.js/wrangler.json:

{
  "compatibility_date": "2024-09-19",
  "pages_build_output_dir": ".."
}

Modules

pnpm nitro build playground --preset cloudflare_module

.output/server/wrangler.json:

{
  "compatibility_date": "2024-09-19",
  "main": "index.mjs",
  "assets": {
    "binding": "ASSETS",
    "directory": "../public"
  }
}