Allow returning Response from onRequest callback

[paveldubovitsky]

Description

Currently, middleware can only modify requests before they are sent to the server. There's no way to short-circuit the middleware chain and return a response immediately, which is useful for cases like deduplicating or caching responses to avoid unnecessary network requests.

Proposal

Allow middleware's onRequest hook to return a Response object. When a middleware returns a Response:

• The request is not sent to the server
• Subsequent onRequest handlers are skipped
• onResponse handlers are skipped

Example usage:

// Simple cache middleware example
const createCacheMiddleware = (): Middleware => {
  const cache = new Map<string, Response>();
  const getCacheKey = (request: Request) => `${request.method}:${request.url}`;
  
  return {
    async onRequest({ request }) {
      const key = getCacheKey(request);
      const cached = cache.get(key);
      if (cached) {
        // Return cached response, skipping actual request and remaining middleware chain
        return cached.clone();
      }
    },
    async onResponse({ request, response }) {
      if (response.ok) {
        const key = getCacheKey(request);
        cache.set(key, response);
      }
    }
  };
};

Checklist

• I’m willing to open a PR for this (see CONTRIBUTING.md)

[drwpow]

Oh this is clever! To be honest, I just have never thought of this, but I can see the usefulness of this.

I think you’ve proposed a clear usecase of why someone would want this, and this API seems to be backwards-compatible enough I think we could add in without disrupting anyone. Since onRequest() doesn’t return a response currently, this wouldn’t a breaking change.

Would happily accept a PR for this following your proposal