docs: add cloudflare workers section

[Hebilicious]

Cloudflare Workers is going to be in the future the main way to deploy application on Cloudflare, presenting it first makes sense. This also includes some re-organizing of the cloudflare pages section.

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

[pi0]

The current config and docs are valid 💯

Thinking would be better advise new users to use the new managed deployConfig feature flag.

export default defineNuxtConfig({
  compatibilityDate: "2025-03-01",
  nitro: { cloudflare: { nodeCompat: true, deployConfig: true } }
});

It generates all proper config (including compat flags and asset binding with valid path).

Cloudflare starter template for Nuxt already updated with this and Nitro docs should be updated as well.

[Hebilicious]

The current config and docs are valid 💯

Thinking would be better advise new users to use the new managed deployConfig feature flag.

export default defineNuxtConfig({
  compatibilityDate: "2025-03-01",
  nitro: { cloudflare: { nodeCompat: true, deployConfig: true } }
});

It generates all proper config (including compat flags and asset binding with valid path).

Cloudflare starter template for Nuxt already updated with this and Nitro docs should be updated as well.

I don't mind making the change, but what is the behaviour of this flag ?
If I'm adding anything custom to my wrangler.jsonc, such as a route or observability, does deployConfig override wrangler.jsonc? Or does it merges some properties with a user provided one?

Should we meet in the middle and recommend in this docs using deployConfig as an alternative to the user controlled wrangler.jsonc ? There's a subset of user that definitely prefer avoiding the abstractions.

[pi0]

Yes, it will be merged if the user config exists.

We had been working with the cloudflare team for months to achieve this functionality (that is the default for the ongoing vite plugin and new nitro) -- it is only not enabled today because cloudflare needs safer migration for existing deployments.

[Hebilicious]

@pi0 got it, I made changes to recommend the use of these flags and provided more context.

[emily-shen]

Left some comments from the Cloudflare side, thanks so much for putting up this PR 🧡

[emily-shen]

Should we add a local dev step?

2. Develop your project locally:

  npx nuxi dev

nitro-cloudflare-dev provides access to local simulators of Cloudflare bindings. It is currently experimental.

We would need to add modules: ["nitro-cloudflare-dev"] to the nuxt config above as well.

---

Or we could add a preview step after build that just runs npx wrangler dev :)

[Hebilicious]

Great suggestion, I've added that as a tip.
@pi0 it's not available through nuxi add module due to being experimental? Because this would be a really smooth way to add the module.