chore(cloudflare): fix typo

[V1RE]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ 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

The cloudflare unenv preset had a small typo: unencCfNodeCompat, so fixed that to be unenvCfNodeCompat to match the rest.

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[vercel]

@V1RE is attempting to deploy a commit to the Nitro Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

📝 Walkthrough

Walkthrough

Renames the exported preset constant from unencCfNodeCompat to unenvCfNodeCompat in the Cloudflare preset module. The import and usage of this constant are updated accordingly to reflect the new identifier name across related files.

Changes

Cohort / File(s)	Summary
Cloudflare preset constant rename src/presets/cloudflare/unenv/preset.ts	Renamed exported constant unencCfNodeCompat to unenvCfNodeCompat
Cloudflare utils import and usage update src/presets/cloudflare/utils.ts	Updated import statement and function usage to reference the renamed constant unenvCfNodeCompat

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

This is a straightforward identifier renaming across a minimal set of files with no logic or behavioral changes involved.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows conventional commits format with a type prefix (chore) and clear description of a typo fix.
Description check	✅ Passed	The description clearly relates to the changeset, explaining the typo fix from unencCfNodeCompat to unenvCfNodeCompat.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0c3150d and db78af2.

📒 Files selected for processing (2)

• src/presets/cloudflare/unenv/preset.ts (1 hunks)
• src/presets/cloudflare/utils.ts (2 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-12-03T19:09:13.877Z

Learnt from: medz
Repo: nitrojs/nitro PR: 3834
File: src/presets/cloudflare/server-entry.ts:63-63
Timestamp: 2025-12-03T19:09:13.877Z
Learning: In the Nitro Cloudflare preset (src/presets/cloudflare/server-entry.ts), native errors from oxc-parser and Node.js readFile operations should be allowed to bubble up naturally without wrapping, as their native error messages are more user-friendly and provide better diagnostic information.

Applied to files:

• src/presets/cloudflare/unenv/preset.ts
• src/presets/cloudflare/utils.ts

🧬 Code graph analysis (1)

src/presets/cloudflare/utils.ts (1)

src/presets/cloudflare/unenv/preset.ts (1)

• unenvCfNodeCompat (6-26)

🔇 Additional comments (2)

src/presets/cloudflare/utils.ts (1)

19-19: Import and usage correctly updated to the new preset name

The import of unenvCfNodeCompat and its use in enableNodeCompat are consistent with the renamed export, with no behavioral changes to how the unenv preset is applied.

Also applies to: 195-195

src/presets/cloudflare/unenv/preset.ts (1)

6-6: Verify no remaining references to the old identifier

The rename to unenvCfNodeCompat appears consistent with the unenv namespace convention. However, this change should be verified by searching the codebase to ensure no stale references to the old identifier remain.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}