Problem

getRequestIP silently ignores event.context.clientAddress. Writing to the documented type surface — clientAddress is declared on H3EventContext (src/types/context.ts:27) — never reaches the reader at src/utils/request.ts:542, which reads event.req.context?.clientAddress. The call falls through to event.req.ip instead.

app.get("/", (event) => {
  event.context.clientAddress = "9.9.9.9";
  return getRequestIP(event); // undefined (expected "9.9.9.9")
});

Root cause

The invariant event.context === event.req.context is supposed to hold, but the constructor never established it. Two adjacent PRs conspired:

• feat: inherit req.context and ServerRequestContext types #1194 changed the ctor to this.context = context || req.context || new EmptyObject() — reading req.context as a fallback source, but never writing the resolved value back to req.context.
• feat: HTTPEvent for more agnostic usage #1195 then moved the getRequestIP reader from event.context.clientAddress onto event.req.context?.clientAddress, assuming the two were always the same object.

They only coincide when the runtime pre-populated req.context — and srvx does not do so by default, so the common path diverges. The ?. masked the breakage as a silent undefined.

Fix

Assign the resolved context back to req.context so both point at one object across all three construction paths (explicit context, inherited req.context, fresh fallback):

this.context = req.context = context || req.context || new EmptyObject();

Tests

Added regression tests in test/unit/event.test.ts:

• event.context === event.req.context when neither is provided
• same reference when an explicit context is passed
• pre-populated req.context is reused
• getRequestIP observes clientAddress written to event.context

All three failing-before assertions pass after the fix; full suite (1581 tests) + lint/typecheck green.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Bug Fixes

  • Ensured request and event context consistently reference the same object.
  • Preserved existing request context or applied the provided context when available.
  • Improved client IP retrieval when the address is stored in the event context.

• Tests

  • Added coverage for context sharing, reuse, and client IP behavior.