src/utils/body.ts (1)

258-260: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Export and reuse isBodyLimitError instead of duplicating the ERR_BODY_TOO_LARGE check. Both sites independently test the same error shape against the same magic string with no shared source of truth.

• src/utils/body.ts#L258-L260: export isBodyLimitError (drop the file-local visibility) so it can be imported elsewhere.
• src/response.ts#L108-L119: import isBodyLimitError from src/utils/body.ts and replace the inline (val as { code?: string }).code !== "ERR_BODY_TOO_LARGE" check with !isBodyLimitError(val).

♻️ Proposed refactor

--- a/src/utils/body.ts
-/** Whether an error was thrown by the srvx body-size limiter. */
-function isBodyLimitError(error: unknown): boolean {
+/** Whether an error was thrown by the srvx body-size limiter. */
+export function isBodyLimitError(error: unknown): boolean {
   return (error as { code?: string } | undefined)?.code === "ERR_BODY_TOO_LARGE";
 }

--- a/src/response.ts
+import { isBodyLimitError } from "./utils/body.ts";
...
-    if (!isHTTPError && (val as { code?: string }).code !== "ERR_BODY_TOO_LARGE") {
+    if (!isHTTPError && !isBodyLimitError(val)) {

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/utils/body.ts` around lines 258 - 260, Export isBodyLimitError from
src/utils/body.ts so it is reusable, then import it in src/response.ts and
replace the inline ERR_BODY_TOO_LARGE check with !isBodyLimitError(val). Update
both affected sites: src/utils/body.ts lines 258-260 and src/response.ts lines
108-119, preserving the existing response behavior.

src/utils/internal/body.ts (1)

42-45: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Use an options object for the new helper.

Expose the limit as { limit } and update its caller to avoid positional-argument drift.

As per coding guidelines: “Use options object as second parameter for multi-argument functions.”

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/utils/internal/body.ts` around lines 42 - 45, Update the limitBody helper
to accept an options object containing the limit property instead of a
positional numeric argument, and update every caller to pass { limit }
accordingly. Preserve the existing body-limiting behavior.

Source: Coding guidelines

src/utils/internal/body.ts (1)

40-43: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Use an options object for the limit configuration.

Change this to limitBody(body, { limit }) and update its caller so the internal API remains extensible.

As per coding guidelines, use an options object as the second parameter for multi-argument functions.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/utils/internal/body.ts` around lines 40 - 43, Update limitBody to accept
a second-parameter options object containing limit instead of a numeric limit,
and adjust its caller to invoke it with { limit }. Preserve the existing
body-limiting behavior while keeping the internal API extensible.

Source: Coding guidelines

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

src/utils/internal/body.ts (1)

31-70: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Use options objects for both limiting helpers.

• src/utils/internal/body.ts#L31-L70: Change limitBody(body, limit) to accept { limit }.
• src/utils/internal/body.ts#L95-L95: Change limitRequestBody(req, limit) to accept { limit }, then update call sites.

As per coding guidelines, “Use options object as second parameter for multi-argument functions.”

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@src/utils/internal/body.ts` around lines 31 - 70, Update limitBody to accept
an options object containing limit instead of a positional second argument, and
update limitRequestBody similarly to accept { limit }. Adjust every call site of
both helpers to pass the new options-object form while preserving existing
request-body limiting behavior.

Source: Coding guidelines

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes