feat(vercel, netlify, cloudflare): support req.ip

[huseeiin]

add more ip support :)

[vercel]

@huseeiin 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

Updates add client IP extraction and runtime initialization across Netlify, Vercel (Node & Web), and Cloudflare presets; Netlify handler signature tightened to ServerRequest and ISR/context access adjusted.

Changes

Cohort / File(s)	Summary
Netlify runtime src/presets/netlify/runtime/netlify.ts	Handler signature changed to async (req: ServerRequest). Ensures req.runtime = { name: "netlify" } when missing, sets req.ip from x-nf-client-connection-ip, and reads ISR options from req.context.
Vercel runtimes src/presets/vercel/runtime/vercel.node.ts, src/presets/vercel/runtime/vercel.web.ts	Node: overrides req.socket.remoteAddress via Object.defineProperty, sourcing IP from x-forwarded-for. Web: initializes full req.runtime = { name: "vercel", vercel: { context } } and defines lazy req.ip that reads x-forwarded-for.
Cloudflare runtime src/presets/cloudflare/runtime/_module-handler.ts	augmentReq now assigns req.ip from the cf-connecting-ip header (or undefined if absent) before further request augmentation.
Manifests / metadata manifest_file, package.json	Minor manifest/package metadata edits (few lines changed).

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Possibly related PRs

• feat(cloudflare): always augment request with cf context #3904 — Modifies Cloudflare request augmentation and adds cf-connecting-ip → req.ip handling; directly related to Cloudflare changes in this PR.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ 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%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title follows conventional commits format with scope (vercel, netlify, cloudflare) and clear description of the feature being added (req.ip support).
Description check	✅ Passed	The description relates to the changeset by indicating the PR adds IP support, which aligns with the file changes adding req.ip properties across multiple platforms.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/nitrojs/nitro@3952

commit: c058924

[pi0]

/cc @QuiiBz do you think of any better way for Node.js style handler? (can't we rely on original remoteAddress? i see it is currently always 127.0.0.1)