What was the reason for removing req, res from context?
What was the exact reason for doing so?
While implementing a simple rate limiter like this: https://github.com/vercel/next.js/tree/canary/examples/api-routes-rate-limit
I found a use case where I needed the res object, because of which I had to change the context to include it, similar to how it was before. Is there some other way around this or would it be better to bring it back?
While implementing a simple rate limiter like this: https://github.com/vercel/next.js/tree/canary/examples/api-routes-rate-limit
I found a use case where I needed the res object, because of which I had to change the context to include it, similar to how it was before. Is there some other way around this or would it be better to bring it back?
GitHub
The React Framework. Contribute to vercel/next.js development by creating an account on GitHub.
