You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Custom servers are actively discouraged by the NextJs team, and for pretty good reasons. It was a "hack" in some sense, that this package used for quite some time to support specific cookie/middleware/redirect functionality.
I won't be actively maintaining support for custom servers, because now that we have rewrites and have removed our Express dependency, they simply aren't necessary. All version previous to v5.0.0 support custom servers, and can be used as long as you'd like – no need to refactor immediately.
For an idea of what an upgrade path would look like, you can check: #689 (comment). I'm hoping to gather more information like this and update the docs.
Why would you remove the custom server support?
I use custom route patterns and some other middlewares in my project (eg. also next-i18next).
From v5.0 it makes it extremely hard for me to update this package since I would probably rewrite and refactor a lot of code.
Isn't it possible to return the middleware functionality for custom servers ?
The text was updated successfully, but these errors were encountered: