This PR is the initiative of deprecating the edge runtime. Proxy will
default to Node.js runtime, and will not allow runtime config. If the
users want to use the edge runtime, they should stay on the Middleware,
though we recommend starting the migration.
---------
Co-authored-by: devjiwonchoi <devjiwonchoi@gmail.com>
Co-authored-by: JJ Kasper <jj@jjsweb.site>
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>
JJ Kasper