Feature Request: Bun.serve.error with Request parameter

[SaltyAom]

What is the problem this feature would solve?

Current Bun.serve.error only provides an Error as a callback while fetch accepts request

Bun.serve({
    port: 3000,
    fetch(request) {
        throw new Error('thing')
    },
    error(error) {
        return new Response('thing')
    }
})

This makes error a "generic catch-all function" instead of being able to be tailored to a specific need for each request, similar to fetch. Leaving error unused most of the time

Bun.serve({
    port: 3000,
    fetch(request) {
        try {
            throw new Error('thing')
        } catch (error) {
            return handleErrorForEachRequest(request)
        }
    },
    error(error) {
        // Unable to tailor based on request, default to try-catch inside fetch
        return new Response('thing')
    }
})

What is the feature you are proposing to solve the problem?

Add request as a 2nd parameter to error callback

This wouldn't introduce any breaking change with any prior versions

Bun.serve({
    port: 3000,
    fetch(request) {
        throw new Error('thing')
    },
    // Request is added here
    error(error, request) {
        return handleErrorForEachRequest(request)
    }
})

What alternatives have you considered?

Keep using try-catch as provided

[github-actions]

Found 2 possible duplicate issues:

1. get data from request in Bun.serve Error handler #15475
2. Bun.serve error callback is missing the request #9015

This issue will be automatically closed as a duplicate in 3 days.

• If your issue is a duplicate, please close it and 👍 the existing issue instead
• To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

[robobun]

✅ Done — error(error, request) lands in #29565. Works for both fetch and routes: handlers; the old error(error) signature keeps working unchanged.