mirror of
https://github.com/vercel/next.js.git
synced 2026-09-20 02:25:18 +08:00
Jiwon Choi
d7a58203d1
We recommend users avoid relying on Middleware unless no other options exist. Our goal is to give them APIs with better ergonomics so they can achieve their goals without Middleware. The term “middleware” often confuses users with Express.js middleware, which can encourage misuse. To clarify our direction, we are renaming the file convention to “proxy.” This highlights that we are moving away from Middleware, breaking down its overloaded features, and making the Proxy clear in its purpose. `proxy.js` should be a drop-in replacement for `middleware.js` for its features, but ONE thing: ```diff - export function middleware + export function proxy ``` Codemod: https://github.com/vercel/next.js/pull/84127 --------- Co-authored-by: Benjamin Woodruff <benjamin.woodruff@vercel.com>
7 lines
133 B
JavaScript
7 lines
133 B
JavaScript
export default (req, res) => {
|
|
return res
|
|
.status(200)
|
|
.setHeader('headers-from-serverless', '1')
|
|
.json(req.headers)
|
|
}
|